From: Waiman Long <longman@redhat.com>
To: Shaojie Sun <sunshaojie@kylinos.cn>
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
mkoutny@suse.com, ridong.chen@linux.dev, shuah@kernel.org,
tj@kernel.org
Subject: Re: [PATCH v2] cgroup/cpuset: Add test for partition root invalidation returning wrong CPUs
Date: Tue, 11 Aug 2026 14:33:56 -0400 [thread overview]
Message-ID: <19c86abc-feb7-409c-b2f6-6eafdcaa4c76@redhat.com> (raw)
In-Reply-To: <20260811095848.365138-1-sunshaojie@kylinos.cn>
On 8/11/26 5:58 AM, Shaojie Sun wrote:
> Add a test case to REMOTE_TEST_MATRIX covering the bug fixed by
> commit 345f40166694 ("cgroup/cpuset: Return only actually allocated
> CPUs during partition invalidation"). The test verifies that when a
> sibling partition root changes its cpuset.cpus to overlap with another
> partition root, only actually allocated CPUs (effective_xcpus) are
> returned to the parent, not all CPUs in cpus_allowed.
>
> Signed-off-by: Shaojie Sun <sunshaojie@kylinos.cn>
> ---
> tools/testing/selftests/cgroup/test_cpuset_prs.sh | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/testing/selftests/cgroup/test_cpuset_prs.sh b/tools/testing/selftests/cgroup/test_cpuset_prs.sh
> index 0d41aa0d343d..236cb1b38178 100755
> --- a/tools/testing/selftests/cgroup/test_cpuset_prs.sh
> +++ b/tools/testing/selftests/cgroup/test_cpuset_prs.sh
> @@ -502,6 +502,12 @@ REMOTE_TEST_MATRIX=(
> " C1-4:P1 . C1-2:P1 C1-3:P2 . . \
> . . P0 C2-3 . . p1:1,4|c11:1|c12:2-3 \
> p1:P1|c11:P0|c12:P2 2-3"
> + # Changing a sibling partition's cpuset.cpus to overlap with another
> + # sibling partition should invalidate itself and return only actually
> + # allocated CPUs (effective_xcpus) to the parent.
> + " C1-4:P1 . C1-2:P1 C2-4:P2 . . \
> + . . . C1-2 . . p1:3-4|c11:1-2|c12:3-4 \
> + p1:P1|c11:P1|c12:P-2"
> )
>
> #
Reviewed-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2026-08-11 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:59 [PATCH] " Shaojie Sun
2026-08-10 17:58 ` Waiman Long
2026-08-11 9:58 ` [PATCH v2] " Shaojie Sun
2026-08-11 18:33 ` Waiman Long [this message]
2026-08-12 2:26 ` 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=19c86abc-feb7-409c-b2f6-6eafdcaa4c76@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--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=sunshaojie@kylinos.cn \
--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
all inboxes | Powered by JetHome®