syzbot


possible deadlock in __dev_queue_xmit (2)
Status: auto-closed as invalid on 2019/11/19 09:01
Reported-by: syzbot+f8c40b4da41f3e8049c4@syzkaller.appspotmail.com
First crash: 571d, last: 456d
similar bugs (7):
Kernel Title Repro Bisected Count Last Reported Patched Status
android-49 possible deadlock in __dev_queue_xmit 4 485d 555d 0/3 auto-closed as invalid on 2019/10/25 08:36
upstream possible deadlock in __dev_queue_xmit (3) C cause 79 18d 322d 0/17 upstream: reported C repro on 2019/12/03 09:55
linux-4.19 possible deadlock in __dev_queue_xmit C 2 4d14h 81d 0/1 upstream: reported C repro on 2020/07/31 07:05
android-414 possible deadlock in __dev_queue_xmit 3 544d 555d 0/1 auto-closed as invalid on 2019/10/21 21:31
android-44 possible deadlock in __dev_queue_xmit 14 321d 382d 0/2 auto-closed as invalid on 2020/04/02 07:14
linux-4.14 possible deadlock in __dev_queue_xmit 7 31d 476d 0/1 upstream: reported on 2019/07/02 00:39
upstream possible deadlock in __dev_queue_xmit 1 643d 643d 0/17 closed as invalid on 2019/03/10 18:51

Sample crash report:

Crashes (2):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Maintainers
ci-upstream-bpf-next-kasan-gce 2019/07/22 09:00 bpf-next 192f0f8e b3c615f5 .config log report
ci-upstream-net-kasan-gce 2019/03/28 12:34 net-next 356d71e0 f94f56fe .config log report davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, xiyou.wangcong@gmail.com