From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Chen Ridong" <chenridong@huaweicloud.com>,
"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>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH/for-next 1/2] cgroup/cpuset: Defer housekeeping_update() call from CPU hotplug to task_work
Date: Wed, 28 Jan 2026 07:44:49 -1000 [thread overview]
Message-ID: <aXpLEcOFhuGYGPY-@slm.duckdns.org> (raw)
In-Reply-To: <20260128044251.1229702-2-longman@redhat.com>
On Tue, Jan 27, 2026 at 11:42:50PM -0500, Waiman Long wrote:
> +static void isolation_task_work_fn(struct callback_head *cb)
> +{
> + cpuset_full_lock();
> + __update_isolation_cpumasks(true);
> + cpuset_full_lock();
^
unlock?
Thanks.
--
tejun
next prev parent reply other threads:[~2026-01-28 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 4:42 [PATCH/for-next 0/2] cgroup/cpuset: Fix partition related locking issues Waiman Long
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 [this message]
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=aXpLEcOFhuGYGPY-@slm.duckdns.org \
--to=tj@kernel.org \
--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=longman@redhat.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox