syzbot


possible deadlock in start_this_handle (2)
Status: auto-closed as invalid on 2021/07/13 16:11
Reported-by: syzbot+bfdded10ab7dcd7507ae@syzkaller.appspotmail.com
First crash: 260d, last: 223d
similar bugs (1):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in start_this_handle 8 1105d 1143d 0/22 auto-closed as invalid on 2019/04/13 16:27

Sample crash report:

Crashes (8):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-qemu-upstream 2021/03/10 18:14 upstream 280d542f6ffa 764067f3 .config log report info possible deadlock in start_this_handle
ci-qemu-upstream 2021/03/07 13:07 upstream 280d542f6ffa c599ed12 .config log report info possible deadlock in start_this_handle
ci-qemu-upstream 2021/02/20 23:50 upstream f40ddce88593 3e5ed8b4 .config log report info possible deadlock in start_this_handle
ci-qemu-upstream 2021/02/19 18:57 upstream f40ddce88593 f689d40a .config log report info possible deadlock in start_this_handle
ci-qemu-upstream-386 2021/03/15 16:11 upstream 280d542f6ffa fdb2bb2c .config log report info possible deadlock in start_this_handle
ci-qemu-upstream-386 2021/02/21 18:58 upstream 55f62bc87347 a659b3f1 .config log report info possible deadlock in start_this_handle
ci-qemu-upstream-386 2021/02/19 20:00 upstream f40ddce88593 f689d40a .config log report info possible deadlock in start_this_handle
ci-qemu-upstream-386 2021/02/06 13:29 upstream 1e0d27fce010 23a562df .config log report info possible deadlock in start_this_handle