syzbot


WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
Status: auto-closed as invalid on 2020/08/13 01:44
Reported-by: syzbot+ee9b387c5b896f32b37b@syzkaller.appspotmail.com
First crash: 566d, last: 552d
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected C 2126 1261d 1275d 6/22 fixed on 2018/05/08 18:30
upstream WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2) C done 640 287d 405d 21/22 fixed on 2021/03/10 01:49

Sample crash report:

Crashes (4):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-linux-4-14 2020/04/15 01:43 linux-4.14.y c10b57a567e4 3f3c5574 .config log report
ci2-linux-4-14 2020/04/12 13:46 linux-4.14.y 4520f06b03ae 36b0b050 .config log report
ci2-linux-4-14 2020/04/10 15:43 linux-4.14.y 4520f06b03ae a8c6a3f8 .config log report
ci2-linux-4-14 2020/04/01 00:59 linux-4.14.y 01364dad1d45 a34e2c33 .config log report