[PATCH] init_reap_node() initialization fix

It looks like there is a bug in init_reap_node() in slab.c that can cause
multiple oops's on certain ES7000 configurations. The variable reap_node
is defined per cpu, but only initialized on a single CPU. This causes an
oops in next_reap_node() when __get_cpu_var(reap_node) returns the wrong
value. Fix is below.

Signed-off-by: Dan Yeisley <dan.yeisley@unisys.com>
Cc: Andi Kleen <ak@suse.de>
Acked-by: Christoph Lameter <clameter@engr.sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Manfred Spraul <manfred@colorfullife.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

authored by Daniel Yeisley and committed by Linus Torvalds 7f6b8876 d13adb60

+1 -1
+1 -1
mm/slab.c
··· 883 883 if (node == MAX_NUMNODES) 884 884 node = first_node(node_online_map); 885 885 886 - __get_cpu_var(reap_node) = node; 886 + per_cpu(reap_node, cpu) = node; 887 887 } 888 888 889 889 static void next_reap_node(void)