From: Ming Lei <ming.lei@redhat.com>
To: Heorhi Valakhanovich <code@mail.geov.name>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [blk-mq] Kernel OOPS after usb drive surprise remove (bisected)
Date: Mon, 8 Sep 2025 08:28:48 +0800 [thread overview]
Message-ID: <aL4jQG-_CeHxGPsU@fedora> (raw)
In-Reply-To: <LmKwxMZhQ0h6bHWk_m7EMu4jDpbdcL0Z4gix3USIvS2sJpGZP1b_858GvxaDL6zwoGxrPIs-dT10NLxersJpxExsOOpJmyDh_fTOp97ZBYE=@mail.geov.name>
On Sun, Sep 07, 2025 at 02:48:27PM +0000, Heorhi Valakhanovich wrote:
> Kernel version 6.16.4 and later.
>
> Usb3 thumb drive surprise removal triggers an oops in blk_mq_free_map_and_rqs.
> Block IO is limping afterwards and often system is unusable.
>
>
> Bisected to:
>
> commit f9a9098ca82612006b9c71ce03b8fe189a437370 (HEAD)
> Author: Ming Lei <ming.lei@redhat.com>
> Date: Fri Aug 15 21:17:37 2025 +0800
>
> blk-mq: fix lockdep warning in __blk_mq_update_nr_hw_queues
>
> [ Upstream commit 2d82f3bd8910eb65e30bb2a3c9b945bfb3b6d661 ]
No, that is not true, because scsi/usb does not call into
blk_mq_update_nr_hw_queues().
>
>
> relevant kernel log:
>
> Sep 07 17:19:26: BUG: kernel NULL pointer dereference, address: 0000000000000020
> Sep 07 17:19:26: #PF: supervisor read access in kernel mode
> Sep 07 17:19:26: #PF: error_code(0x0000) - not-present page
> Sep 07 17:19:26: PGD 0 P4D 0
Please try the following fix:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-6.18/block&id=ba28afbd9eff2a6370f23ef4e6a036ab0cfda409
Thanks,
Ming
next prev parent reply other threads:[~2025-09-08 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 14:48 [blk-mq] Kernel OOPS after usb drive surprise remove (bisected) Heorhi Valakhanovich
2025-09-08 0:28 ` Ming Lei [this message]
2025-09-08 11:53 ` Heorhi Valakhanovich
2025-09-22 10:21 ` Heorhi Valakhanovich
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=aL4jQG-_CeHxGPsU@fedora \
--to=ming.lei@redhat.com \
--cc=code@mail.geov.name \
--cc=linux-block@vger.kernel.org \
/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