Linux cgroups development
 help / color / mirror / Atom feed
From: Zhang Qiao <zhangqiao22@huawei.com>
To: Waiman Long <longman@redhat.com>
Cc: jifa@huawei.com, "Hui Tang" <tanghui20@huawei.com>,
	cgroups@vger.kernel.org, "Johannes Weiner" <hannes@cmpxchg.org>,
	ridong.chen@linux.dev, "Michal Koutný" <mkoutny@suse.com>,
	"Tejun Heo" <tj@kernel.org>
Subject: Re: [BUG] cgroup/cpuset: Concurrent WARN_ON_ONCE triggers during remote partition stress-test
Date: Tue, 1 Sep 2026 10:25:57 +0800	[thread overview]
Message-ID: <9a6a4965-7ac7-d4e5-918d-4f1abb3dce9b@huawei.com> (raw)
In-Reply-To: <6cb9d419-fc2d-410a-9362-527e2bd9b33b@redhat.com>



在 2026/8/31 22:18, Waiman Long 写道:
> On 8/31/26 5:05 AM, Zhang Qiao wrote:
>> Hi,
>>
>> While stress-testing cpuset partitions under KASAN (kernel 7.2-rc1,
>> dc59e4fea9d83 "Linux 7.2-rc1"), four distinct WARN_ON_ONCE() in
>> kernel/cgroup/cpuset.c fire within a ~1s window. They all concern the
>> remote partition / effective-cpumask invariants and are triggered by
>> concurrent CPU hotplug, cpuset.cpus/cpuset.cpus.exclusive/
>> cpuset.cpus.partition writes, task migration and (un)partitioning of
>> nested subgroups.
>>
>> Environment
>> -----------
>> - Kernel : Linux 7.2-rc1, generic KASAN enabled, x86_64, PREEMPT
>> - server   : Intel Xeon Platinum 8380 @ 2.30GHz, 2 NUMA nodes, 160 CPUs
>> - Cmdline: ... cgroup_disable=files apparmor=0    
>> systemd.unified_cgroup_hierarchy=1
>>
>> Reproduction
>> ------------
>> A pure-shell self-contained script (attached below) runs several concurrent
>> "disturbance" loops. The issue is extremely easy to reproduce; the script
>> consistently triggers the WARNs within seconds of execution.
>>
>>    - CPU hotplug toggle of a helper pool (CPU online/offline)
>>    - random writes to cpuset.cpus / cpuset.cpus.exclusive
>>      (single CPU, empty, or range)
>>    - random root <-> member switching of cpuset.cpus.partition
>>    - migrating burner tasks between subgroups via cgroup.procs
>>    - creating and removing nested sub-partitions under S0-S3
> 
> Thank for reporting the bug. It is recently known that there are bugs in the
> handling of nested sub-partitions. We are in the process of getting it fixed.
> 
> Cheers,
> Longman

Hi Waiman,

Thanks for the update!

I'm looking forward to the fix. Please CC me when the patch is ready, and I'll
be happy to test it on my end.

Thanks,
Zhang Qiao

> 
> 
> .

      reply	other threads:[~2026-09-01  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  9:05 [BUG] cgroup/cpuset: Concurrent WARN_ON_ONCE triggers during remote partition stress-test Zhang Qiao
2026-08-31 14:18 ` Waiman Long
2026-09-01  2:25   ` Zhang Qiao [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=9a6a4965-7ac7-d4e5-918d-4f1abb3dce9b@huawei.com \
    --to=zhangqiao22@huawei.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jifa@huawei.com \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --cc=tanghui20@huawei.com \
    --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