Re: [PATCH v2 2/6] mm, mempolicy: stop adjusting current->il_next in mpol_rebind_nodemask()
From: Christoph Lameter <hidden>
Date: 2017-05-17 15:07:37
Also in:
cgroups, linux-mm, lkml
On Wed, 17 May 2017, Vlastimil Babka wrote:
The task->il_next variable stores the next allocation node id for task's MPOL_INTERLEAVE policy. mpol_rebind_nodemask() updates interleave and bind mempolicies due to changing cpuset mems. Currently it also tries to make sure that current->il_next is valid within the updated nodemask. This is bogus, because 1) we are updating potentially any task's mempolicy, not just current, and 2) we might be updating a per-vma mempolicy, not task one.
Reviewed-by: Christoph Lameter <redacted>