linux-kernel - [patch 4/3] cpusets: memory_spread_user interleaves over all mems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.0.9999.0710251933490.2989@chino.kir.corp.google.com>
Date:	Thu, 25 Oct 2007 19:34:42 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Andi Kleen <ak@...e.de>, Paul Jackson <pj@....com>,
	Christoph Lameter <clameter@....com>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	linux-kernel@...r.kernel.org
Subject: [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 <ak@...e.de>
Cc: Paul Jackson <pj@....com>
Cc: Christoph Lameter <clameter@....com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@...com>
Signed-off-by: David Rientjes <rientjes@...gle.com>
---
 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/