From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: Prevent leakage of isolated CPUs into sched domains
Date: Wed, 11 Dec 2024 05:46:37 -1000 [thread overview]
Message-ID: <Z1mz3Rh221Lbcinv@slm.duckdns.org> (raw)
In-Reply-To: <20241205195101.31108-1-longman@redhat.com>
On Thu, Dec 05, 2024 at 02:51:01PM -0500, Waiman Long wrote:
> Isolated CPUs are not allowed to be used in a non-isolated partition.
> The only exception is the top cpuset which is allowed to contain boot
> time isolated CPUs.
>
> Commit ccac8e8de99c ("cgroup/cpuset: Fix remote root partition creation
> problem") introduces a simplified scheme of including only partition
> roots in sched domain generation. However, it does not properly account
> for this exception case. This can result in leakage of isolated CPUs
> into a sched domain.
>
> Fix it by making sure that isolated CPUs are excluded from the top
> cpuset before generating sched domains.
>
> Also update the way the boot time isolated CPUs are handled in
> test_cpuset_prs.sh to make sure that those isolated CPUs are really
> isolated instead of just skipping them in the tests.
>
> Fixes: ccac8e8de99c ("cgroup/cpuset: Fix remote root partition creation problem")
> Signed-off-by: Waiman Long <longman@redhat.com>
Applied to cgroup/for-6.13-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2024-12-11 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 19:51 [PATCH] cgroup/cpuset: Prevent leakage of isolated CPUs into sched domains Waiman Long
2024-12-11 15:46 ` Tejun Heo [this message]
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=Z1mz3Rh221Lbcinv@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=shuah@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