[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYulmBtfi3A9TJZu@kbusch-mbp>
Date: Tue, 10 Feb 2026 14:39:36 -0700
From: Keith Busch <kbusch@...nel.org>
To: "Ionut Nechita (Wind River)" <ionut.nechita@...driver.com>
Cc: axboe@...nel.dk, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org,
ming.lei@...hat.com, muchun.song@...ux.dev,
mkhalfella@...estorage.com, sunlightlinux@...il.com,
chris.friesen@...driver.com, stable@...r.kernel.org,
ionut_n2001@...oo.com, bigeasy@...utronix.de
Subject: Re: [PATCH v2 1/1] block/blk-mq: fix RT kernel regression with
dedicated quiesce_sync_lock
On Tue, Feb 10, 2026 at 10:49:46PM +0200, Ionut Nechita (Wind River) wrote:
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 0ad3dd3329db7..888718a782f88 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -171,7 +171,7 @@ bool __blk_freeze_queue_start(struct request_queue *q,
> percpu_ref_kill(&q->q_usage_counter);
> mutex_unlock(&q->mq_freeze_lock);
> if (queue_is_mq(q))
> - blk_mq_run_hw_queues(q, false);
> + blk_mq_run_hw_queues(q, true);
I didn't see the reasoning for this path to run in async mode. Is this
change related to this patch?
Powered by blists - more mailing lists