Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795052750; b=ohJlHafVtSo+PrvU3++SjnsTPiT+ssmF8lLEm+j8deCvnvMEdQvoIhbSexfWk4xGD2db nDTUG0ZQnRDNKogpKzZSmqbjehGm7s1r9anhXI2kR8+iaZn1LGru9v8rBAPaeYahExMiv Xaiq9YeY5IVNJVmGq/UKfRAI+w3n1xjNQpiDUI6P6Apq3Ma9pxWPnBFHwnKGox+ZTLE0f gjYUX8zdx/284pw+Zu5fnIE8mCVDGwrRQj5YExyIqvQkTu6U6RsXnuatq5wAHzAhLaGyV klrXIAQbuQRZLiNoGm5ZYpQGjXASrR4y166ry5CODjEmgf1J1tFK7snFX9WilP8iCcA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795052750; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=9psr0YMNvGjYMqvvcfNDzkXz7OUgQysuGK6Rfe0gb6o=; b=kg+vMKbwTOrpOxmauNwNMTF9zxl2Tg/vmWh7dw6RH8MmNhuacxYQwFEKf42hzj7oK2WY DrXMexjhd17io8ca4aDHgg3VBpyowouprtUzXpNmougOG4zTW0oilk5xMJqDH0Hh1UUVg RE9e95gn+zGfLOrLs+vZuFLKIjQoRhsHpdRh9G1NjfIs2kpRcf0zdEvVdMyVkjKi1JaU4 OAvNC/Uv0ljavMGpmQjLhPDi48dhNFpveM0Fe9vReI+2TwFwK4bFAv1IYBVJJmxOiaV6d Rf7txu3O9oGQ/e5KjXrAPH6QhteSJA9fJOXd7i62czdSUIdtIWCUGG5DwdDgB8QqKkg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b="YmJKVwk/"; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6658F606A325; Thu, 19 Nov 2026 01:45:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=YmJKVwk/ Received: by smtp.kernel.org (Postfix) with ESMTPSA id 70D901F000C4; Thu, 19 Nov 2026 01:45:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795052750; bh=9psr0YMNvGjYMqvvcfNDzkXz7OUgQysuGK6Rfe0gb6o=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=YmJKVwk/4dr0+2iWzIU9+mCPfl5nYb2j/IzmC+yQTi3sE+9wBWZ6GNUHPBd9r58Gs CNNFU2JReTmedRXi6pF6HiyCvqhqtFtKMtOyC778TkOtja9uS6cER/fuwD2M0opoOs yEXk2kbIAPqGIzc9hPL4fT7PwT4nyg19gTTjBKus= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Nirmoy Das , Jens Axboe , Sasha Levin Subject: [PATCH 5.15 0673/2214] blk-mq: clear stale inactive flag on hctx reuse Date: Wed, 18 Nov 2026 15:39:09 +0100 Message-ID: <20261118150038.738466973@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261118150009.797899913@linuxfoundation.org> References: <20261118150009.797899913@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 5.15-stable review patch. If anyone has any objections, please let me know. ------------------ From: Nirmoy Das [ Upstream commit afc1de47a7ab607ae6403c4bfda36b0bf3cd342f ] When the last CPU mapped to an hctx goes offline, blk_mq_hctx_notify_offline() sets BLK_MQ_S_INACTIVE. Updating the number of hardware queues exits every hctx and parks it on q->unused_hctx_list. A later update can reuse a parked hctx through blk_mq_alloc_and_init_hctx(), at any queue index, and nothing clears the flag. If the reused hctx is mapped to an online CPU, blk_mq_get_tag() keeps returning BLK_MQ_NO_TAG for it. __blk_mq_alloc_requests() sleeps and retries, expecting CPU hotplug to move the task to another CPU, so a task that stays on that CPU never gets a tag. Onlining the original CPU doesn't recover it either, because blk_mq_hctx_notify_online() only clears the flag on the hctx that CPU now maps to. Clear BLK_MQ_S_INACTIVE in blk_mq_init_hctx() so a reused hctx starts like a freshly allocated one. A reused hctx has no cpuhp instances at that point, so the offline callback can't set the flag again before blk_mq_add_hw_queues_cpuhp() registers it. Clearing the flag in blk_mq_exit_hctx() is not enough, because a parked hctx keeps its cpuhp instances until blk_mq_remove_hw_queues_cpuhp(). Preserve the other hctx state flags. Reproduced with null_blk on v7.3 in a four-vCPU arm64 QEMU/KVM guest: modprobe null_blk nr_devices=0 mkdir /sys/kernel/config/nullb/nullb0 cd /sys/kernel/config/nullb/nullb0 echo 4 > submit_queues; echo 1 > memory_backed; echo 16 > size echo 1 > power echo 0 > /sys/devices/system/cpu/cpu3/online echo 2 > submit_queues echo 4 > submit_queues Offlining CPU3 marks hctx3 inactive. After the two updates it comes back as hctx1 and is mapped to CPU0: # cat /sys/block/nullb0/mq/1/cpu_list 0 # cat /sys/kernel/debug/block/nullb0/hctx1/state INACTIVE A 4K O_DIRECT read pinned to CPU0 hangs in D state, while the same read on CPU1 and CPU2 completes. Onlining CPU3 again leaves hctx1 inactive and the CPU0 read still hangs. With this change hctx1 state is empty and the reads on CPU0, CPU1 and CPU2 complete, before and after onlining CPU3. Fixes: bf0beec0607d ("blk-mq: drain I/O when all CPUs in a hctx are offline") Cc: stable@vger.kernel.org Assisted-by: LLM Signed-off-by: Nirmoy Das Link: https://patch.msgid.link/20261020125129.430600-1-nirmoyd@nvidia.com Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin --- block/blk-mq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/block/blk-mq.c b/block/blk-mq.c index 17795b3ae7f33..62ccdc6f7a093 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -2771,6 +2771,7 @@ static int blk_mq_init_hctx(struct request_queue *q, struct blk_mq_hw_ctx *hctx, unsigned hctx_idx) { hctx->queue_num = hctx_idx; + clear_bit(BLK_MQ_S_INACTIVE, &hctx->state); if (!(hctx->flags & BLK_MQ_F_STACKING)) cpuhp_state_add_instance_nocalls(CPUHP_AP_BLK_MQ_ONLINE, -- 2.53.0