linux-kernel - Re: [PATCH v2 2/2] block: Fix WARN_ON in blk_mq_run_hw

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]

Message-Id: <4006496F-8A9D-492E-8264-6B1FE7910C20@linux.dev>
Date: Tue, 23 Dec 2025 10:18:39 +0800
From: Muchun Song <muchun.song@...ux.dev>
To: "Ionut Nechita (WindRiver)" <djiony2011@...il.com>
Cc: ming.lei@...hat.com,
 axboe@...nel.dk,
 gregkh@...uxfoundation.org,
 ionut.nechita@...driver.com,
 linux-block@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 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 Dec 23, 2025, at 04:15, Ionut Nechita (WindRiver) <djiony2011@...il.com> 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.
> 
> The issue happens during device removal/scanning when:
> 1. blk_mq_destroy_queue() -> blk_queue_start_drain()
> 2. blk_freeze_queue_start() calls blk_mq_run_hw_queues(q, false)
> 3. This triggers the warning in blk_mq_run_hw_queue() when in interrupt context
> 
> Change the synchronous call to asynchronous to avoid running in interrupt context.
> 
> Fixes: Warning in blk_mq_run_hw_queue+0x1fa/0x260

You've added a wrong format of Fixes tag.

Thanks.

> Signed-off-by: Ionut Nechita <ionut.nechita@...driver.com>