From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: Waiman Long <longman@redhat.com>, cgroups@vger.kernel.org
Cc: ridong.chen@linux.dev, tj@kernel.org, hannes@cmpxchg.org,
mkoutny@suse.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Guopeng Zhang <zhangguopeng@kylinos.cn>
Subject: Re: [PATCH 08/17] cgroup/cpuset: Release CPUs when a type change is rejected
Date: Wed, 26 Aug 2026 13:53:04 +0800 [thread overview]
Message-ID: <62da6156-138a-4d2e-8384-0bc21481e351@linux.dev> (raw)
In-Reply-To: <0a9afea3-bd0c-42af-8c92-6f2d54348d1e@redhat.com>
在 2026/8/24 22:37, Waiman Long 写道:
> On 8/20/26 8:41 AM, Guopeng Zhang wrote:
>> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>>
>> When a housekeeping check rejects a root-to-isolated or isolated-to-root
>> change, update_prstate() marks the partition invalid but leaves its
>> effective_xcpus allocated. Those CPUs remain missing from the partition
>> which owns the invalidated subtree.
>>
>> Disable a rejected remote partition with remote_partition_disable().
>> For a local partition, return effective_xcpus to its parent before
>> recording the invalid state. Use the complete mask because descendants
>> are invalidated along with the parent and their CPUs return at the same
>> time.
>>
>> Fixes: 103b08709e8a ("cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping")
>> Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
>> ---
>> kernel/cgroup/cpuset.c | 15 +++++++++++++--
>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index 853942c1afeb..a616012927be 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -3020,10 +3020,21 @@ static int update_prstate(struct cpuset *cs, int new_prs)
>> compute_partition_owned_cpumask(cs, tmpmask.new_cpus);
>> if (((new_prs == PRS_ISOLATED) &&
>> !isolated_cpus_can_update(tmpmask.new_cpus, NULL)) ||
>> - prstate_housekeeping_conflict(new_prs, tmpmask.new_cpus))
>> + prstate_housekeeping_conflict(new_prs, tmpmask.new_cpus)) {
>> err = PERR_HKEEPING;
>> - else
>> + if (is_remote_partition(cs)) {
>> + WRITE_ONCE(cs->prs_err, err);
> This WRITE_ONCE() is not necessary as it will be done later in the function.
>> + remote_partition_disable(cs, &tmpmask);
>> + } else {
>> + spin_lock_irq(&callback_lock);
>> + partition_xcpus_del(old_prs, parent, cs->effective_xcpus);
>> + spin_unlock_irq(&callback_lock);
>> + cpuset_update_tasks_cpumask(parent, tmpmask.new_cpus);
>> + update_sibling_cpumasks(parent, cs, &tmpmask);
>> + }
>
> This code to disable the partition is duplicating what is being done in the last else clause of the outer if, but in a somewhat different way. That is not good programming practice. You can either jump to the partition disabling code below or separate out the partition disabling code controlled by a separate control flag and set the flag to do it.
>
Agreed. I removed the redundant WRITE_ONCE() and used a
disable_partition flag to share the existing partition-disable path in
v2.
Thanks,
Guopeng
> Cheers,
> Longman
>
>> + } else {
>> isolcpus_updated = true;
>> + }
>> } else {
>> /*
>> * Switching back to member is always allowed even if it
>
next prev parent reply other threads:[~2026-08-26 5:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 12:41 [PATCH 00/17] cgroup/cpuset: Fix partition CPU ownership and isolation accounting Guopeng Zhang
2026-08-20 12:41 ` [PATCH 01/17] selftests/cgroup: Drop invalid boot isolation comparison Guopeng Zhang
2026-08-20 12:41 ` [PATCH 02/17] cgroup/cpuset: Preserve boot-isolated CPUs on partition release Guopeng Zhang
2026-08-20 12:41 ` [PATCH 03/17] selftests/cgroup: Test boot-isolated CPU " Guopeng Zhang
2026-08-20 12:41 ` [PATCH 04/17] cgroup/cpuset: Limit type-change accounting to owned CPUs Guopeng Zhang
2026-08-24 14:24 ` Waiman Long
2026-08-26 5:44 ` Guopeng Zhang
2026-08-20 12:41 ` [PATCH 05/17] selftests/cgroup: Test isolated CPU accounting on type changes Guopeng Zhang
2026-08-20 12:41 ` [PATCH 06/17] cgroup/cpuset: Validate type changes against owned CPUs Guopeng Zhang
2026-08-24 14:25 ` Waiman Long
2026-08-26 5:48 ` Guopeng Zhang
2026-08-20 12:41 ` [PATCH 07/17] selftests/cgroup: Test type-change validation with child-owned CPUs Guopeng Zhang
2026-08-24 14:31 ` Waiman Long
2026-08-26 5:51 ` Guopeng Zhang
2026-08-20 12:41 ` [PATCH 08/17] cgroup/cpuset: Release CPUs when a type change is rejected Guopeng Zhang
2026-08-24 14:37 ` Waiman Long
2026-08-26 5:53 ` Guopeng Zhang [this message]
2026-08-20 12:41 ` [PATCH 09/17] selftests/cgroup: Test rejected partition type changes Guopeng Zhang
2026-08-20 12:41 ` [PATCH 10/17] cgroup/cpuset: Fix isolated accounting on direct child invalidation Guopeng Zhang
2026-08-20 12:41 ` [PATCH 11/17] selftests/cgroup: Test isolation " Guopeng Zhang
2026-08-20 12:41 ` [PATCH 12/17] cgroup/cpuset: Invalidate children outside the new CPU mask Guopeng Zhang
2026-08-25 15:11 ` Waiman Long
2026-08-20 12:41 ` [PATCH 13/17] selftests/cgroup: Test child invalidation after shrinking cpuset.cpus Guopeng Zhang
2026-08-20 12:41 ` [PATCH 14/17] cgroup/cpuset: Publish cpus_allowed before partition updates Guopeng Zhang
2026-08-20 12:42 ` [PATCH 15/17] selftests/cgroup: Test shrinking cpuset.cpus in a remote partition Guopeng Zhang
2026-08-20 12:42 ` [PATCH 16/17] cgroup/cpuset: Fix isolated accounting on propagated invalidation Guopeng Zhang
2026-08-20 12:42 ` [PATCH 17/17] selftests/cgroup: Test isolation " Guopeng Zhang
2026-08-21 2:48 ` [PATCH 00/17] cgroup/cpuset: Fix partition CPU ownership and isolation accounting Ridong Chen
2026-08-21 3:17 ` Guopeng Zhang
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=62da6156-138a-4d2e-8384-0bc21481e351@linux.dev \
--to=guopeng.zhang@linux.dev \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=zhangguopeng@kylinos.cn \
/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®