From: Greg KH <gregkh@linuxfoundation.org>
To: Saranya Muruganandam <saranyamohan@google.com>
Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
Ming Lei <ming.lei@redhat.com>,
stable@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Zhang Wensheng <zhangwensheng@huaweicloud.com>,
Zhong Jinghua <zhongjinghua@huawei.com>,
Hillf Danton <hdanton@sina.com>, Yu Kuai <yukuai3@huawei.com>,
Dennis Zhou <dennis@kernel.org>
Subject: Re: [PATCH] block: fix use-after-free of q->q_usage_counter
Date: Fri, 22 Sep 2023 11:26:22 +0200 [thread overview]
Message-ID: <2023092258-clothing-passerby-e0f2@gregkh> (raw)
In-Reply-To: <20230921182012.3965572-1-saranyamohan@google.com>
On Thu, Sep 21, 2023 at 11:20:12AM -0700, Saranya Muruganandam wrote:
> From: Ming Lei <ming.lei@redhat.com>
>
> commit d36a9ea5e7766961e753ee38d4c331bbe6ef659b upstream.
>
> For blk-mq, queue release handler is usually called after
> blk_mq_freeze_queue_wait() returns. However, the
> q_usage_counter->release() handler may not be run yet at that time, so
> this can cause a use-after-free.
>
> Fix the issue by moving percpu_ref_exit() into blk_free_queue_rcu().
> Since ->release() is called with rcu read lock held, it is agreed that
> the race should be covered in caller per discussion from the two links.
>
> Backport-notes: Not a clean cherry-pick since a lot has changed,
> however essentially the same fix.
>
> Reported-by: Zhang Wensheng <zhangwensheng@huaweicloud.com>
> Reported-by: Zhong Jinghua <zhongjinghua@huawei.com>
> Link: https://lore.kernel.org/linux-block/Y5prfOjyyjQKUrtH@T590/T/#u
> Link: https://lore.kernel.org/lkml/Y4%2FmzMd4evRg9yDi@fedora/
> Cc: Hillf Danton <hdanton@sina.com>
> Cc: Yu Kuai <yukuai3@huawei.com>
> Cc: Dennis Zhou <dennis@kernel.org>
> Fixes: 2b0d3d3e4fcf ("percpu_ref: reduce memory footprint of percpu_ref in fast path")
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> Link: https://lore.kernel.org/r/20221215021629.74870-1-ming.lei@redhat.com
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Saranya Muruganandam <saranyamohan@google.com>
> ---
> block/blk-core.c | 2 --
> block/blk-sysfs.c | 2 ++
> 2 files changed, 2 insertions(+), 2 deletions(-)
What stable kernel(s) are you expecting this backport to be applied to?
thanks,
greg "not a mind reader" k-h
next prev parent reply other threads:[~2023-09-22 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 18:20 [PATCH] block: fix use-after-free of q->q_usage_counter Saranya Muruganandam
2023-09-21 20:32 ` kernel test robot
2023-09-22 1:09 ` Ming Lei
2023-09-22 9:26 ` Greg KH [this message]
2023-09-22 18:21 ` Saranya Muruganandam
2023-10-07 10:22 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 2:16 Ming Lei
2022-12-15 12:25 ` 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=2023092258-clothing-passerby-e0f2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=dennis@kernel.org \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=saranyamohan@google.com \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yukuai3@huawei.com \
--cc=zhangwensheng@huaweicloud.com \
--cc=zhongjinghua@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.