Re: [syzbot] [block?] possible deadlock in blk_mq_submit_bio

syzbot
2024-11-27T05:59:32Z

> On Sat, Nov 23, 2024 at 11:37 PM syzbot
> <syzbot+5218c85078236fc46227@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 06afb0f36106 Merge tag 'trace-v6.13' of git://git.kernel.o..
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=148bfec0580000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=b011a14ee4cb9480
>> dashboard link: https://syzkaller.appspot.com/bug?extid=5218c85078236fc46227
>> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>> userspace arch: i386
>>
>> Unfortunately, I don't have any reproducer for this issue yet.
>>
>> Downloadable assets:
>> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-06afb0f3.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/aae0561fd279/vmlinux-06afb0f3.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/faa3af3fa7ce/bzImage-06afb0f3.xz
> ...
>
>> If the report is already addressed, let syzbot know by replying with:
>> #syz fix: exact-commit-title
>>
>> If you want to overwrite report's subsystems, reply with:
>> #syz set subsystems: new-subsystem
>> (See the list of subsystem names on the web dashboard)
>>
>> If the report is a duplicate of another one, reply with:
>> #syz dup: exact-subject-of-another-report
>
> #syz test: https://github.com/ming1/linux v6.13/block-fix

This crash does not have a reproducer. I cannot test it.

>