[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aUnu1HdMqQbksLeY@fedora>
Date: Tue, 23 Dec 2025 09:22:28 +0800
From: Ming Lei <ming.lei@...hat.com>
To: "Ionut Nechita (WindRiver)" <djiony2011@...il.com>
Cc: axboe@...nel.dk, gregkh@...uxfoundation.org,
ionut.nechita@...driver.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, muchun.song@...ux.dev,
sashal@...nel.org, stable@...r.kernel.org
Subject: Re: [PATCH v2 2/2] block: Fix WARN_ON in blk_mq_run_hw_queue when
called from interrupt context
On Mon, Dec 22, 2025 at 10:15:41PM +0200, Ionut Nechita (WindRiver) wrote:
> From: Ionut Nechita <ionut.nechita@...driver.com>
>
> Fix warning "WARN_ON_ONCE(!async && in_interrupt())" that occurs during
> SCSI device scanning when blk_freeze_queue_start() calls blk_mq_run_hw_queues()
> synchronously from interrupt context.
Can you show the whole stack trace in the warning? The in-code doesn't
indicate that freeze queue can be called from scsi's interrupt context.
Thanks,
Ming
Powered by blists - more mailing lists