linux-kernel - Re: [syzbot] upstream boot error: BUG: unable to handle kernel paging request in blk_mq_map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 26 Aug 2022 09:29:36 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     Aleksandr Nogikh <nogikh@...gle.com>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        syzbot <syzbot+ea55456e1ff28ef7f9ff@...kaller.appspotmail.com>,
        Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>, llvm@...ts.linux.dev,
        'Aleksandr Nogikh' via syzkaller-bugs 
        <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel paging
 request in blk_mq_map_swqueue

On 8/26/22 06:15, Aleksandr Nogikh wrote:
> Syzbot would have included the USB mailing list and the USB
> maintainers if it saw that the bug might be related to this subsystem.
> The bot's guess was that it was the BLOCK LAYER subsystem, so it Cc'd
> only the general lists and linux-block@...r.kernel.org
> 
> Is there anything in this bug report that can reliably indicate that
> the bug has to do with USB? If there is, we can definitely adjust our
> guilty subsystem recognition logic.

Hi Aleksandr,
  I may have been to fast with my conclusion that the root cause is in 
the USB subsystem.

Regarding your question, can syzbot inspect the console log and scan for 
"scsi host%d: %s" strings? The text next to the colon comes from the 
SCSI host template "name" member and hence indicates which SCSI LLD 
driver is involved.

Thanks,

Bart.