summaryrefslogtreecommitdiff
path: root/scripts/basic/split-include.c
diff options
context:
space:
mode:
authorWaiman Long <longman@redhat.com>2026-10-25 19:53:59 -0400
committerTejun Heo <tj@kernel.org>2026-10-26 07:44:36 -1000
commitec0254b9eb49ebc9383dc3ae5cb69c8606f88499 (patch)
treedbae1006fcbc6d326e9b7832f3be406f5e8addba /scripts/basic/split-include.c
parenta7d89d92fdfbceb678d82710135d4eee2623d727 (diff)
downloadlinux-ec0254b9eb49ebc9383dc3ae5cb69c8606f88499.tar.gz
linux-ec0254b9eb49ebc9383dc3ae5cb69c8606f88499.zip
cgroup/cpuset: Release invalid isolated CPUs with a shrunk root partition parent
It is also reported by sashiko that there may be leakages of isolated CPUs when a root partition parent shrinks its effective_xcpus with isolated partition children. Leakage here means that isolated_cpus may contain extra CPUs that are not in any isolated partitions and not boot time isolated. Those CPUs cannot be used in any isolated partitions anymore. There are 2 different cases here. The effective_xcpus becomes empty and the isolated partition should be invalidated in this case. Alternatively some of its effective_xcpus are not in parent's effective xcpus but still have some valid effective_xcpus left. The isolated partition can remain valid. In both cases, the invalid isolated CPUs will have to be released from isolated_cpus if appropriate. Fix that by calling isolated_cpus_release() to release those isolated CPUs from isolated_cpus. New test cases are added to test_cpuset_prs.sh to test this. Fixes: 11e5f407b64a ("cgroup/cpuset: Keep track of CPUs in isolated partitions") Signed-off-by: Waiman Long <longman@redhat.com> Reviewed-by: Guopeng Zhang <zhangguopeng@kylinos.cn> Tested-by: Guopeng Zhang <zhangguopeng@kylinos.cn> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/basic/split-include.c')
0 files changed, 0 insertions, 0 deletions