diff options
| author | Gregory Price (Meta) <gourry@gourry.net> | 2026-10-19 12:21:38 -0400 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-10-19 13:08:12 -1000 |
| commit | b0cec62d2867ab3ed27604d5c177b8960c43b17a (patch) | |
| tree | 866a4b83785af0b2e3877ff1f00c63c847b507a3 /scripts/Makefile.thinlto | |
| parent | 1850c669516cb8568150937497a9a16a7bfa1582 (diff) | |
| download | linux-next-b0cec62d2867ab3ed27604d5c177b8960c43b17a.tar.gz linux-next-b0cec62d2867ab3ed27604d5c177b8960c43b17a.zip | |
cgroup/cpuset: use mems_allowed_seq when checking a policy nodemask
A cpuset update changes the task's mems_allowed and rebinds its
mempolicy in separate steps under mems_allowed_seq, but the check
reads both without it. This can cause a spurious numa placement
miss under some cpuset/mempolicy combinations.
A reader that loads one mask before the update and the other after
it can see a spurious empty intersection and drop the nodemask.
For example, a task with cpuset.mems={0} and MPOL_BIND={0}. If the
cpuset moves to mems={1,2}, the policy is rebound to {1}.
The allocator can race and compare the old mems_allowed {0} against
the new policy {1} - which will result in a dropped nodemask and a
misplaced allocation on node 2.
Simply retry the intersection until mems_allowed_seq is stable.
This covers the task policy, which is rebound under mems_allowed_seq.
VMA policies are rebound afterwards by mpol_rebind_mm(), outside
mems_allowed_seq, and are not covered by this change.
Fixes: cc9a6c877661 ("cpuset: mm: reduce large amounts of memory barrier related damage v3")
Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
