fix OOM killing processes wrongly thought MPOL_BIND
commit3d124cbba316737af8f3a6959edb95bbd130a4d8
authorHugh Dickins <hugh@veritas.com>
Mon, 23 Apr 2007 21:41:02 +0000 (23 14:41 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Tue, 24 Apr 2007 15:23:07 +0000 (24 08:23 -0700)
tree273350d3ce14b1252ff79fd24efa43f39161a200
parentfdc30b3d448bf86dd45f9df3e8ac0d36a3bdd9b2
fix OOM killing processes wrongly thought MPOL_BIND

I only have CONFIG_NUMA=y for build testing: surprised when trying a memhog
to see lots of other processes killed with "No available memory
(MPOL_BIND)".  memhog is killed correctly once we initialize nodemask in
constrained_alloc().

Signed-off-by: Hugh Dickins <hugh@veritas.com>
Acked-by: Christoph Lameter <clameter@sgi.com>
Acked-by: William Irwin <bill.irwin@oracle.com>
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/oom_kill.c