From: Greg KH <gregkh@linuxfoundation.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: Tejun Heo <tj@kernel.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: Mon, 1 Sep 2025 08:06:24 +0200 [thread overview]
Message-ID: <2025090113-matcher-scoured-ab39@gregkh> (raw)
In-Reply-To: <afc56d3b-1fc7-48b8-a724-7abc59e06cdd@huaweicloud.com>
On Mon, Sep 01, 2025 at 09:38:49AM +0800, Chen Ridong wrote:
>
>
> On 2025/8/26 1:32, Tejun Heo wrote:
> > Hello, Greg.
> >
> > On Sat, Aug 23, 2025 at 08:43:48AM +0200, Greg KH wrote:
> >>> Applied to cgroup/for-6.17-fixes.
> >>
> >> Both or just this second patch? Should I take the first through the
> >> driver-core tree, or do you want to take it through the cgroup tree? No
> >> objection from me for you to take both :)
> >
> > Sorry about the lack of clarity. Just the second one. The first one looks
> > fine to me but it would probably be more appropriate if you take it.
> >
> > Thanks!
> >
>
> Hello all,
>
> Any other opinions? Can this patch be applied?
Please give us a chance to catch up with patch reviews :)
prev parent reply other threads:[~2025-09-01 6:06 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
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 [this message]
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=2025090113-matcher-scoured-ab39@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--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=tj@kernel.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).