From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhong Jinghua <zhongjinghua@huawei.com>,
Yu Kuai <yukuai3@huawei.com>, Dennis Zhou <dennis@kernel.org>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/3] lib/percpu-refcount: fix use-after-free by late ->release
Date: Wed, 14 Dec 2022 10:50:58 +0800 [thread overview]
Message-ID: <20221214025101.1268437-1-ming.lei@redhat.com> (raw)
Hi,
The pattern of wait_event(percpu_ref_is_zero()) may cause
percpu_ref_exit() to be called before ->release() is done, so
user-after-free may be caused, fix the issue by draining ->release()
in percpu_ref_exit().
Ming Lei (3):
lib/percpu-refcount: support to exit refcount automatically during
releasing
lib/percpu-refcount: apply PERCPU_REF_AUTO_EXIT
lib/percpu-refcount: drain ->release() in perpcu_ref_exit()
drivers/infiniband/ulp/rtrs/rtrs-srv.c | 4 +--
include/linux/percpu-refcount.h | 36 ++++++++++++++++++++++++--
lib/percpu-refcount.c | 31 +++++++++++++++++++---
mm/memcontrol.c | 5 ++--
4 files changed, 66 insertions(+), 10 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-14 2:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 2:50 Ming Lei [this message]
2022-12-14 2:50 ` [PATCH 1/3] lib/percpu-refcount: support to exit refcount automatically during releasing Ming Lei
2022-12-14 2:51 ` [PATCH 2/3] lib/percpu-refcount: apply PERCPU_REF_AUTO_EXIT Ming Lei
2022-12-14 2:51 ` [PATCH 3/3] lib/percpu-refcount: drain ->release() in perpcu_ref_exit() Ming Lei
2022-12-15 16:54 ` Tejun Heo
2022-12-16 23:06 ` kernel test robot
2022-12-17 0:37 ` kernel test robot
2022-12-17 7:32 ` kernel test robot
[not found] ` <20221214081651.954-1-hdanton@sina.com>
2022-12-14 13:30 ` Ming Lei
2022-12-14 16:07 ` Dennis Zhou
2022-12-15 0:34 ` Ming Lei
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=20221214025101.1268437-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dennis@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yukuai3@huawei.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 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®