From: Chen Ridong <chenridong@huaweicloud.com>
To: longman@redhat.com, tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com
Subject: Re: [PATCH -next v3] cpuset: Treat cpusets in attaching as populated
Date: Fri, 21 Nov 2025 08:39:24 +0800 [thread overview]
Message-ID: <af6ef663-2a80-4cb7-9702-65ec285bd8a2@huaweicloud.com> (raw)
In-Reply-To: <20251114020847.1040546-1-chenridong@huaweicloud.com>
On 2025/11/14 10:08, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> Currently, the check for whether a partition is populated does not
> account for tasks in the cpuset of attaching. This is a corner case
> that can leave a task stuck in a partition with no effective CPUs.
>
> The race condition occurs as follows:
>
> cpu0 cpu1
> //cpuset A with cpu N
> migrate task p to A
> cpuset_can_attach
> // with effective cpus
> // check ok
>
> // cpuset_mutex is not held // clear cpuset.cpus.exclusive
> // making effective cpus empty
> update_exclusive_cpumask
> // tasks_nocpu_error check ok
> // empty effective cpus, partition valid
> cpuset_attach
> ...
> // task p stays in A, with non-effective cpus.
>
> To fix this issue, this patch introduces cs_is_populated, which considers
> tasks in the attaching cpuset. This new helper is used in validate_change
> and partition_is_populated.
>
> Fixes: e2d59900d936 ("cgroup/cpuset: Allow no-task partition to have empty cpuset.cpus.effective")
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
> ---
> kernel/cgroup/cpuset.c | 35 +++++++++++++++++++++++++++--------
> 1 file changed, 27 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index daf813386260..8bf7c38ba320 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -356,6 +356,15 @@ static inline bool is_in_v2_mode(void)
> (cpuset_cgrp_subsys.root->flags & CGRP_ROOT_CPUSET_V2_MODE);
> }
>
> +static inline bool cpuset_is_populated(struct cpuset *cs)
> +{
> + lockdep_assert_held(&cpuset_mutex);
> +
> + /* Cpusets in the process of attaching should be considered as populated */
> + return cgroup_is_populated(cs->css.cgroup) ||
> + cs->attach_in_progress;
> +}
> +
> /**
> * partition_is_populated - check if partition has tasks
> * @cs: partition root to be checked
> @@ -373,19 +382,29 @@ static inline bool is_in_v2_mode(void)
> static inline bool partition_is_populated(struct cpuset *cs,
> struct cpuset *excluded_child)
> {
> - struct cgroup_subsys_state *css;
> - struct cpuset *child;
> + struct cpuset *cp;
> + struct cgroup_subsys_state *pos_css;
>
> - if (cs->css.cgroup->nr_populated_csets)
> + /*
> + * We cannot call cs_is_populated(cs) directly, as
> + * nr_populated_domain_children may include populated
> + * csets from descendants that are partitions.
> + */
> + if (cs->css.cgroup->nr_populated_csets ||
> + cs->attach_in_progress)
> return true;
>
> rcu_read_lock();
> - cpuset_for_each_child(child, css, cs) {
> - if (child == excluded_child)
> + cpuset_for_each_descendant_pre(cp, pos_css, cs) {
> + if (cp == cs || cp == excluded_child)
> continue;
> - if (is_partition_valid(child))
> +
> + if (is_partition_valid(cp)) {
> + pos_css = css_rightmost_descendant(pos_css);
> continue;
> - if (cgroup_is_populated(child->css.cgroup)) {
> + }
> +
> + if (cpuset_is_populated(cp)) {
> rcu_read_unlock();
> return true;
> }
> @@ -670,7 +689,7 @@ static int validate_change(struct cpuset *cur, struct cpuset *trial)
> * be changed to have empty cpus_allowed or mems_allowed.
> */
> ret = -ENOSPC;
> - if ((cgroup_is_populated(cur->css.cgroup) || cur->attach_in_progress)) {
> + if (cpuset_is_populated(cur)) {
> if (!cpumask_empty(cur->cpus_allowed) &&
> cpumask_empty(trial->cpus_allowed))
> goto out;
Hi TJ,
It seems you have missed this patch?
--
Best regards,
Ridong
next prev parent reply other threads:[~2025-11-21 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:08 Chen Ridong
2025-11-17 20:50 ` Waiman Long
2025-11-18 0:31 ` Chen Ridong
2025-11-21 0:39 ` Chen Ridong [this message]
2025-11-21 2:27 ` 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=af6ef663-2a80-4cb7-9702-65ec285bd8a2@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.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
all inboxes | Powered by JetHome®