diff options
| author | Waiman Long <longman@redhat.com> | 2026-10-19 14:10:12 -0400 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-10-19 13:08:19 -1000 |
| commit | 46b885416c27214072272b85adb898ed91801062 (patch) | |
| tree | 1832ef3b85bb55f637d0d465773fbf1b21538a96 /scripts/Makefile.thinlto | |
| parent | b0cec62d2867ab3ed27604d5c177b8960c43b17a (diff) | |
| download | linux-next-46b885416c27214072272b85adb898ed91801062.tar.gz linux-next-46b885416c27214072272b85adb898ed91801062.zip | |
cgroup/cpuset: Fix a missing isolated_cpus update in update_cpumasks_hier()
It is found that when a local isolated partition is being invalidated
because its parent partition is no longer valid, the isolated_cpus
cpumask may not be properly updated. Those isolated CPUs may or may
not needed to be removed from isolated_cpus depending on if there is
a local isolated partition ancestor that will now own those isolated
CPUs instead.
Fix that by calling a new ancestor_partition() helper to return the
closeset valid partition root ancestor. If that ancestor is PRS_ROOT,
the isolated CPUs will have to be removed from isolated_cpus. For
a PRS_ISOLATED ancestor, the isolated CPUs are checked against
the ancestor's ones to see if any of them should be removed as it is
possible that the invalidation of the parent may be caused by change in
the effective xcpus of that ancestor. If any of the isolated CPUs should
be removed, isolated_cpus_update() will be called under callback_lock.
An existing test case in test_cpuset_prs.sh is modifed and a new one
added to test that.
Fixes: 11e5f407b64a ("cgroup/cpuset: Keep track of CPUs in isolated partitions")
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
