[patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed

Instead of using current's mems_allowed, which may differ from the
mems_allowed of the cpuset being updated, the newmask passed to
mpol_rebind_mm() is used as the interleave mask in the
memory_spread_user case.

Cc: Andi Kleen <[email protected]>
Cc: Paul Jackson <[email protected]>
Cc: Christoph Lameter <[email protected]>
Cc: Lee Schermerhorn <[email protected]>
Signed-off-by: David Rientjes <[email protected]>
---
 mm/mempolicy.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/mm/mempolicy.c b/mm/mempolicy.c
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -1740,7 +1740,7 @@ static void mpol_rebind_policy(struct mempolicy *pol,
 		break;
 	case MPOL_INTERLEAVE:
 		if (current_cpuset_is_spread_user())
-			tmp = cpuset_mems_allowed(current);
+			tmp = *newmask;
 		else
 			nodes_remap(tmp, pol->v.nodes, *mpolmask, *newmask);
 		pol->v.nodes = tmp;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed
    • From: Paul Jackson <[email protected]>

• Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Next by Date: Re: [PATCH] [CRYPTO]: Fix hmac_digest from the SG breakage.
• Previous by thread: [interesting] smattering of possible memory ordering bugs
• Next by thread: Re: [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]