Re: [syzbot] [block?] [trace?] possible deadlock in blk_trace_ioctl
From: syzbot
Date: Sat Jan 11 2025 - 23:34:12 EST
syzbot has bisected this issue to:
commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@xxxxxxxxxx>
Date: Fri Oct 25 00:37:20 2024 +0000
block: model freeze & enter queue as lock for supporting lockdep
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13cd2bc4580000
start commit: 74741a050b79 Add linux-next specific files for 20241107
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=102d2bc4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17cd2bc4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d3ef0574c9dc8b00
dashboard link: https://syzkaller.appspot.com/bug?extid=a3c16289c8c99b02cac1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175f7d5f980000
Reported-by: syzbot+a3c16289c8c99b02cac1@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: f1be1788a32e ("block: model freeze & enter queue as lock for supporting lockdep")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection