syzbot


possible deadlock in pipe_lock (2)
Status: auto-closed as invalid on 2019/10/18 15:02
Reported-by: syzbot+31d8b84465a7cbfd8515@syzkaller.appspotmail.com
First crash: 307d, last: 235d
duplicates (1):
Title Repro Bisected Count Last Reported Patched Status
possible deadlock in ovl_write_iter C 222 218d 441d 0/16 closed as dup on 2019/02/12 15:47
similar bugs (4):
Kernel Title Repro Bisected Count Last Reported Patched Status
upstream possible deadlock in pipe_lock 50806 724d 772d 0/16 closed as invalid on 2018/02/14 14:20
android-49 possible deadlock in pipe_lock 5 49d 242d 0/3 public: reported on 2019/04/14 09:30
linux-4.19 possible deadlock in pipe_lock C fix 2 228d 231d 1/1 fixed on 2019/11/29 10:34
android-44 possible deadlock in pipe_lock C 82 9d09h 242d 0/2 public: reported C repro on 2019/04/14 08:51

Sample crash report:

Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro Maintainers
ci-upstream-kasan-gce-smack-root 2019/04/21 15:01 upstream 9e5de623 b0e8efcb .config log report linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
ci-upstream-kasan-gce-selinux-root 2019/04/17 19:30 upstream fe5cdef2 b0e8efcb .config log report linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
ci-upstream-kasan-gce-root 2019/02/08 19:03 upstream 74e96711 fa6c7b70 .config log report linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk