From: Waiman Long <longman@redhat.com>
To: "Ridong Chen" <ridong.chen@linux.dev>,
"Hui Peng" <benquike@gmail.com>,
"Guopeng Zhang" <guopeng.zhang@linux.dev>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>
Cc: Shuah Khan <shuah@kernel.org>,
Chen Ridong <chenridong@huawei.com>,
cgroups@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4 2/3] cgroup/cpuset: prevent activating local partition over remote one
Date: Mon, 28 Sep 2026 12:13:02 -0400 [thread overview]
Message-ID: <7e8fa7ac-4438-4dea-b3e0-c142523aeab3@redhat.com> (raw)
In-Reply-To: <93e48fe3-d229-4870-af8a-32431d236211@linux.dev>
On 9/27/26 9:40 PM, Ridong Chen wrote:
>
>
> On 9/24/2026 12:27 PM, Hui Peng wrote:
>> Commit 6da580ec656a ("cgroup/cpuset: Don't allow creation of local
>> partition over a remote one") added a check in update_prstate() to
>> reject
>> creating a top-level local partition whose cs->exclusive_cpus intersects
>> subpartitions_cpus.
>>
>> However, if a top-level cgroup A1 has a child A1/A2 enabled as a remote
>> partition on a subset of its exclusive CPUs (X2-3 on A1, CX2-3:P2 on
>> A1/A2), and A1 is then set to "root" (P1, becoming "root invalid" via
>> update_prstate() because its exclusive CPUs intersect
>> subpartitions_cpus)
>> followed by expanding its CPUs to include additional non-remote CPUs
>> (CX1-3), update_cpumask() / update_exclusive_cpumask() calls
>> validate_partition() without going through update_prstate(). Because
>> validate_partition() does not check trialcs->exclusive_cpus against
>> subpartitions_cpus, A1 transitions from "root invalid" to a valid local
>> partition over the existing remote partition A1/A2 and triggers:
>>
>> WARNING: kernel/cgroup/cpuset.c:1943 at
>> update_parent_effective_cpumask+0x189b/0x1fd0
>>
>> Check trialcs->exclusive_cpus against subpartitions_cpus in
>> validate_partition() when !is_partition_valid(cs), and add a regression
>> test case to tools/testing/selftests/cgroup/test_cpuset_prs.sh.
>>
>
> Was this message assisted by an LLM?
>
> It would be helpful if you could provide the reproducer as I replied
> earlier, so that it can be understood more easily and tested.
The provided test case for test-cpuset_prs.sh is supposed to be the
reproducer if you don't have deadline task running in the test system or
the kernel includes the last cpuset patch that I sent out.
Cheers,
Longman
next prev parent reply other threads:[~2026-09-28 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 4:27 [PATCH v4 0/3] cgroup/cpuset: fix exclusive CPU conflict checks for local and remote partitions Hui Peng
2026-09-24 4:27 ` [PATCH v4 1/3] cgroup/cpuset: return PERR_NOCPUS in remote_partition_enable() on subpartitions_cpus conflict Hui Peng
2026-09-25 19:22 ` Waiman Long
2026-09-26 19:11 ` Tejun Heo
2026-09-28 1:25 ` Ridong Chen
2026-09-24 4:27 ` [PATCH v4 2/3] cgroup/cpuset: prevent activating local partition over remote one Hui Peng
2026-09-27 1:45 ` Waiman Long
2026-09-28 1:40 ` Ridong Chen
2026-09-28 16:13 ` Waiman Long [this message]
2026-09-24 4:27 ` [PATCH v4 3/3] cgroup/cpuset: check sibling effective_xcpus in cpus_excl_conflict() Hui Peng
2026-09-27 23:44 ` Waiman Long
2026-09-28 17:30 ` Tejun Heo
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=7e8fa7ac-4438-4dea-b3e0-c142523aeab3@redhat.com \
--to=longman@redhat.com \
--cc=benquike@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=guopeng.zhang@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=shuah@kernel.org \
--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 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.