From: Waiman Long <longman@redhat.com>
To: "Chen Ridong" <chenridong@huawei.com>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Waiman Long <longman@redhat.com>
Subject: [PATCH v3 0/2] cgroup/cpuset: Fix v1 task migration failure from empty cpuset
Date: Tue, 31 Mar 2026 11:11:06 -0400 [thread overview]
Message-ID: <20260331151108.2771560-1-longman@redhat.com> (raw)
v3:
- Drop patch 3
- Further simplify patch 2 by dropping the flag and only check for
v1 cpuset with no CPU to disable security check.
v2:
- Add a new CS_TASKS_OUT flag to signal that task migration out of
empty cpuset is allowed without setsched security check as suggested
by Tejun.
- Add 2 more patches with minor changes.
As it is found that the cpuset v1 task migration out of cpuset with no
CPU can be blocked by a strict security policy, we need to work around
that issue by treating it as an exceptional case that is allowed without
security check in cpuset_can_attach().
Waiman Long (2):
cgroup/cpuset: Simplify setsched decision check in task iteration loop
of cpuset_can_attach()
cgroup/cpuset: Skip security check for hotplug induced v1 task
migration
kernel/cgroup/cpuset.c | 29 ++++++++++++++++++++---------
1 file changed, 20 insertions(+), 9 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-31 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 15:11 Waiman Long [this message]
2026-03-31 15:11 ` [PATCH v3 1/2] cgroup/cpuset: Simplify setsched decision check in task iteration loop of cpuset_can_attach() Waiman Long
2026-03-31 15:11 ` [PATCH v3 2/2] cgroup/cpuset: Skip security check for hotplug induced v1 task migration Waiman Long
2026-03-31 19:22 ` [PATCH v3 0/2] cgroup/cpuset: Fix v1 task migration failure from empty cpuset 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=20260331151108.2771560-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--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