From: Waiman Long <longman@redhat.com>
To: "Ridong Chen" <ridong.chen@linux.dev>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Guopeng Zhang <guopeng.zhang@linux.dev>,
Waiman Long <longman@redhat.com>
Subject: [PATCH-next v4 0/6] cgroup/cpuset: More fix patches
Date: Sun, 15 Nov 2026 20:23:03 -0500 [thread overview]
Message-ID: <20261116012330.2271010-1-longman@redhat.com> (raw)
[v4]
- Drop v3 patch 1 as it is fixed in a different way in patch 5.
- Add a new patch 2 fixing a minor bug reported by sashiko.
- Add patch 4/5 to fix a remote partition hotplug problem reported
by Guopeng.
- Add patch 6 to fix a bug in lockdep_is_cpuset_held().
[v3]
- Drop patch 1, 4 & 5 of v2 as they are merged.
- Update the new patch 1 as suggested by Chen Ridong
- Add a new fix patch 3.
[v2]
- Reorder the series by putting the original patch 4 before patch 2.
- Update the Fixes tags in patch 1 and 5 as suggested by sashiko.
- Update the new patch 3 to remove obsolete WARN_ON_ONCE() and update
comment as reported by sashiko.
- Minor fix to the test case in patch 5 as reported by sashiko.
This patch series contains an additional set of cpuset fix patches.
Waiman Long (6):
cgroup/cpuset: Fix incorrect partition invalidation logic in
cpuset_hotplug_update_tasks()
cgroup/cpuset: excpus parameter of remote_cpus_update() must have at
least 1 active CPU
cgroup/cpuset: Check remote partition underneath before making an
invalid partition valid
cgroup/cpuset: Revert "remove global remote_children list"
cgroup/cpuset: Handle remote partitions before local partitions in
cpuset_handle_hotplug()
cgroup/cpuset: Fix lockdep_is_cpuset_held()
kernel/cgroup/cpuset-internal.h | 10 +-
kernel/cgroup/cpuset-v1.c | 16 +-
kernel/cgroup/cpuset.c | 178 +++++++++++++-----
.../selftests/cgroup/test_cpuset_prs.sh | 6 +-
4 files changed, 149 insertions(+), 61 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-16 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 1:23 Waiman Long [this message]
2026-11-16 1:23 ` [PATCH-next v4 1/6] cgroup/cpuset: Fix incorrect partition invalidation logic in cpuset_hotplug_update_tasks() Waiman Long
2026-11-16 1:23 ` [PATCH-next v4 2/6] cgroup/cpuset: excpus parameter of remote_cpus_update() must have at least 1 active CPU Waiman Long
2026-11-16 3:07 ` Ridong Chen
2026-11-16 3:34 ` Waiman Long
2026-11-16 1:23 ` [PATCH-next v4 3/6] cgroup/cpuset: Check remote partition underneath before making an invalid partition valid Waiman Long
2026-11-16 3:47 ` Ridong Chen
2026-11-16 4:21 ` Waiman Long
2026-11-16 1:23 ` [PATCH-next v4 4/6] cgroup/cpuset: Revert "remove global remote_children list" Waiman Long
2026-11-16 1:23 ` [PATCH-next v4 5/6] cgroup/cpuset: Handle remote partitions before local partitions in cpuset_handle_hotplug() Waiman Long
2026-11-16 1:23 ` [PATCH-next v4 6/6] cgroup/cpuset: Fix lockdep_is_cpuset_held() Waiman Long
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=20261116012330.2271010-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--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=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