From: Greg KH <gregkh@linuxfoundation.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: longman@redhat.com, lizefan.x@bytedance.com, tj@kernel.org,
hannes@cmpxchg.org, cgroups@vger.kernel.org,
stable@vger.kernel.org, lujialin4@huawei.com
Subject: Re: [PATCH] cpuset: Treat cpusets in attaching as populated
Date: Mon, 12 Jan 2026 08:03:16 +0100 [thread overview]
Message-ID: <2026011258-raving-unlovable-5059@gregkh> (raw)
In-Reply-To: <9d2cdae1-178f-454c-b45a-681d782c483c@huaweicloud.com>
On Mon, Jan 12, 2026 at 02:55:53PM +0800, Chen Ridong wrote:
>
>
> On 2026/1/12 14:42, Greg KH wrote:
> > On Mon, Jan 12, 2026 at 02:42:57AM +0000, Chen Ridong wrote:
> >> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > I did not send this :(
> >
> >> 6.6-stable review patch. If anyone has any objections, please let me know.
> >
> > This is already in the 6.6.120 release.
> >
> > thanks,
> >
> > greg k-h
>
> I am sorry for the confusion.
>
> I downloaded and modified the patch, and replied.
>
> My point is that the patch intended for the 6.6.120 release should include an adaptation.
> Specifically, the following block:
>
> [...]
> if (!excluded_child && !cs->nr_subparts_cpus)
> return cgroup_is_populated(cs->css.cgroup);
> [...]
>
> Should be corrected to:
>
> if (!excluded_child && !cs->nr_subparts_cpus)
> - return cgroup_is_populated(cs->css.cgroup);
> + return cpuset_is_populated(cs);
>
Great, can you send a fixup patch for this that we can apply to the next
release?
thanks,
greg k-h
prev parent reply other threads:[~2026-01-12 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109112140.992393920@linuxfoundation.org>
2026-01-12 2:42 ` [PATCH] cpuset: Treat cpusets in attaching as populated Chen Ridong
2026-01-12 3:02 ` Chen Ridong
2026-01-12 6:42 ` Greg KH
2026-01-12 6:55 ` Chen Ridong
2026-01-12 7:03 ` 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=2026011258-raving-unlovable-5059@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=lujialin4@huawei.com \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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