From: Waiman Long <longman@redhat.com>
To: "Chen Ridong" <chenridong@huaweicloud.com>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Valentin Schneider" <vschneid@redhat.com>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Shuah Khan" <shuah@kernel.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: [PATCH/for-next 0/2] cgroup/cpuset: Fix partition related locking issues
Date: Tue, 27 Jan 2026 23:42:49 -0500 [thread overview]
Message-ID: <20260128044251.1229702-1-longman@redhat.com> (raw)
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Honour kthreads
preferred affinity" patch series [1] merged on top and running the
test-cpuset-prs.sh test, a circular locking dependency lockdep splat
was reported. See patch 2 for details.
The following changes are made to resolve this locking problem.
1) Deferring calling housekeeping_update() from CPU hotplug to task work
2) Release cpus_read_lock before calling housekeeping_update()
With these changes, the cpuset test ran to completion with no failure
and no lockdep splat.
[1] https://lore.kernel.org/lkml/20260125224541.50226-1-frederic@kernel.org/
Waiman Long (2):
cgroup/cpuset: Defer housekeeping_update() call from CPU hotplug to
task_work
cgroup/cpuset: Introduce a new top level isolcpus_update_mutex
kernel/cgroup/cpuset.c | 124 ++++++++++++++----
kernel/sched/isolation.c | 4 +-
kernel/time/timer_migration.c | 3 +-
.../selftests/cgroup/test_cpuset_prs.sh | 9 ++
4 files changed, 111 insertions(+), 29 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-28 4:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 4:42 Waiman Long [this message]
2026-01-28 4:42 ` [PATCH/for-next 1/2] cgroup/cpuset: Defer housekeeping_update() call from CPU hotplug to task_work Waiman Long
2026-01-28 17:44 ` Tejun Heo
2026-01-28 18:08 ` Waiman Long
2026-01-29 4:03 ` Chen Ridong
2026-01-29 7:15 ` Chen Ridong
2026-01-30 1:37 ` Waiman Long
2026-01-30 1:39 ` Waiman Long
2026-01-28 4:42 ` [PATCH/for-next 2/2] cgroup/cpuset: Introduce a new top level isolcpus_update_mutex Waiman Long
2026-01-29 8:01 ` Chen Ridong
2026-01-29 8:20 ` Chen Ridong
2026-01-29 20:57 ` Waiman Long
2026-01-30 1:16 ` Chen Ridong
2026-01-29 21:16 ` Waiman Long
2026-01-30 0:56 ` Chen Ridong
2026-01-30 1:35 ` Waiman Long
2026-01-30 1:42 ` Chen Ridong
2026-01-30 3:53 ` Waiman Long
2026-01-30 6:07 ` Chen Ridong
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=20260128044251.1229702-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=anna-maria@linutronix.de \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.