From: Bart Van Assche <bvanassche@acm.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+ea55456e1ff28ef7f9ff@syzkaller.appspotmail.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev,
'Aleksandr Nogikh' via syzkaller-bugs
<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel paging request in blk_mq_map_swqueue
Date: Fri, 26 Aug 2022 09:29:36 -0700 [thread overview]
Message-ID: <5ffb520f-d86f-be3e-4239-2f31c681ede2@acm.org> (raw)
In-Reply-To: <CANp29Y7bgwDzd47E6h8gseYuu5YXF-ABRrhVXFXS-HF7PhF-Dw@mail.gmail.com>
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@vger.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.
prev parent reply other threads:[~2022-08-26 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 3:24 [syzbot] upstream boot error: BUG: unable to handle kernel paging request in blk_mq_map_swqueue syzbot
2022-08-25 17:48 ` Bart Van Assche
2022-08-26 13:15 ` Aleksandr Nogikh
2022-08-26 16:29 ` Bart Van Assche [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ffb520f-d86f-be3e-4239-2f31c681ede2@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nogikh@google.com \
--cc=syzbot+ea55456e1ff28ef7f9ff@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox