From: Hannes Reinecke <hare@suse.de>
To: Yu Kuai <yukuai1@huaweicloud.com>,
yukuai3@huawei.com, axboe@kernel.dk, bvanassche@acm.org,
ming.lei@redhat.com, nilay@linux.ibm.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com
Subject: Re: [PATCH v3 2/2] blk-mq: fix blk_mq_tags double free while nr_requests grown
Date: Fri, 22 Aug 2025 08:02:08 +0200 [thread overview]
Message-ID: <00421980-4602-4fe4-9f54-1345a7709d71@suse.de> (raw)
In-Reply-To: <20250821060612.1729939-3-yukuai1@huaweicloud.com>
On 8/21/25 08:06, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> In the case user trigger tags grow by queue sysfs attribute nr_requests,
> hctx->sched_tags will be freed directly and replaced with a new
> allocated tags, see blk_mq_tag_update_depth().
>
> The problem is that hctx->sched_tags is from elevator->et->tags, while
> et->tags is still the freed tags, hence later elevator exit will try to
> free the tags again, causing kernel panic.
>
> Fix this problem by replacing et->tags with new allocated tags as well.
>
> Noted there are still some long term problems that will require some
> refactor to be fixed thoroughly[1].
>
> [1] https://lore.kernel.org/all/20250815080216.410665-1-yukuai1@huaweicloud.com/
> Fixes: f5a6604f7a44 ("block: fix lockdep warning caused by lock dependency in elv_iosched_store")
>
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> Reviewed-by: Ming Lei <ming.lei@redhat.com>
> Reviewed-by: Nilay Shroff<nilay@linux.ibm.com>
> ---
> block/blk-mq-tag.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> index d880c50629d6..5cffa5668d0c 100644
> --- a/block/blk-mq-tag.c
> +++ b/block/blk-mq-tag.c
> @@ -622,6 +622,7 @@ int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx,
> return -ENOMEM;
>
> blk_mq_free_map_and_rqs(set, *tagsptr, hctx->queue_num);
> + hctx->queue->elevator->et->tags[hctx->queue_num] = new;
> *tagsptr = new;
> } else {
> /*
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-08-22 6:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 6:06 [PATCH v3 0/2] blk-mq: fix update nr_requests regressions Yu Kuai
2025-08-21 6:06 ` [PATCH v3 1/2] blk-mq: fix elevator depth_updated method Yu Kuai
2025-08-21 12:21 ` Nilay Shroff
2025-08-21 14:57 ` Li Nan
2025-08-22 6:00 ` Hannes Reinecke
2025-08-21 6:06 ` [PATCH v3 2/2] blk-mq: fix blk_mq_tags double free while nr_requests grown Yu Kuai
2025-08-21 14:57 ` Li Nan
2025-08-22 6:02 ` Hannes Reinecke [this message]
2025-08-26 6:27 ` [PATCH v3 0/2] blk-mq: fix update nr_requests regressions Yu Kuai
2025-09-05 7:20 ` Yu Kuai
2025-09-05 19:52 ` Jens Axboe
2025-09-05 19:54 ` Jens Axboe
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=00421980-4602-4fe4-9f54-1345a7709d71@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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
all inboxes | Powered by JetHome®