From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: gregkh@linuxfoundation.org, hannes@cmpxchg.org, mkoutny@suse.com,
peterz@infradead.org, zhouchengming@bytedance.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com,
libaokun1@huawei.com
Subject: Re: [PATCH v2 2/2] cgroup/psi: Set of->priv to NULL upon file release
Date: Fri, 22 Aug 2025 07:48:08 -1000 [thread overview]
Message-ID: <aKitWH39wpfTF5st@slm.duckdns.org> (raw)
In-Reply-To: <20250822070715.1565236-3-chenridong@huaweicloud.com>
On Fri, Aug 22, 2025 at 07:07:15AM +0000, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> Setting of->priv to NULL when the file is released enables earlier bug
> detection. This allows potential bugs to manifest as NULL pointer
> dereferences rather than use-after-free errors[1], which are generally more
> difficult to diagnose.
>
> [1] https://lore.kernel.org/cgroups/38ef3ff9-b380-44f0-9315-8b3714b0948d@huaweicloud.com/T/#m8a3b3f88f0ff3da5925d342e90043394f8b2091b
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
Applied to cgroup/for-6.17-fixes.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-08-22 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:07 [PATCH v2 0/2] kernfs: Fix UAF in PSI polling when open file is released Chen Ridong
2025-08-22 7:07 ` [PATCH v2 1/2] kernfs: Fix UAF in " Chen Ridong
2025-08-22 7:47 ` Greg KH
2025-08-22 17:46 ` Tejun Heo
2025-08-23 0:23 ` Chen Ridong
2025-08-22 7:07 ` [PATCH v2 2/2] cgroup/psi: Set of->priv to NULL upon file release Chen Ridong
2025-08-22 17:48 ` Tejun Heo [this message]
2025-08-23 6:43 ` Greg KH
2025-08-25 17:32 ` Tejun Heo
2025-09-01 1:38 ` Chen Ridong
2025-09-01 6:06 ` Greg KH
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=aKitWH39wpfTF5st@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=zhouchengming@bytedance.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;
as well as URLs for NNTP newsgroup(s).