syzbot


possible deadlock in lock_trace (2)
Status: auto-closed as invalid on 2019/10/25 08:41
Reported-by: syzbot+4b7e4be91bb87d4158e5@syzkaller.appspotmail.com
First crash: 1007d, last: 976d
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in lock_trace syz error 42 489d 995d 0/1 upstream: reported syz repro on 2019/04/28 18:16
linux-4.14 possible deadlock in lock_trace C error 146 547d 1004d 0/1 upstream: reported C repro on 2019/04/19 09:51
android-49 possible deadlock in lock_trace C 7424 776d 1012d 0/3 public: reported C repro on 2019/04/12 00:00
upstream possible deadlock in lock_trace C 1847 1028d 1509d 0/22 closed as dup on 2017/12/12 21:59
upstream possible deadlock in lock_trace (3) syz inconclusive done 69 655d 790d 17/22 fixed on 2020/08/18 22:40
android-414 possible deadlock in lock_trace syz 203 1020d 1012d 0/1 public: reported syz repro on 2019/04/12 00:01
android-44 possible deadlock in lock_trace C 41 782d 1012d 0/2 public: reported C repro on 2019/04/11 08:44

Sample crash report:

Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-selinux-root 2019/04/17 03:04 upstream 444fe9913539 b0e8efcb .config log report
ci-upstream-linux-next-kasan-gce-root 2019/05/17 15:22 linux-next b1d6682ef9bb 95dfd515 .config log report
ci-upstream-linux-next-kasan-gce-root 2019/05/12 06:19 linux-next a802303934b3 c017728b .config log report