summaryrefslogtreecommitdiff
path: root/lib/string.c
diff options
context:
space:
mode:
authorDave Hansen <dave@linux.vnet.ibm.com>2008-12-11 08:36:06 (GMT)
committerPaul Mackerras <paulus@samba.org>2008-12-16 02:48:18 (GMT)
commita4c74ddd5ea3db53fc73d29c222b22656a7d05be (patch)
tree1c2d49c9e3c74fbe612ff7fda74770d24f51e154 /lib/string.c
parent48f797de550d39ea35552646c34149991362ff7f (diff)
downloadlinux-fsl-qoriq-a4c74ddd5ea3db53fc73d29c222b22656a7d05be.tar.xz
powerpc: Fix bootmem reservation on uninitialized node
careful_allocation() was calling into the bootmem allocator for nodes which had not been fully initialized and caused a previous bug: http://patchwork.ozlabs.org/patch/10528/ So, I merged a few broken out loops in do_init_bootmem() to fix it. That changed the code ordering. I think this bug is triggered by having reserved areas for a node which are spanned by another node's contents. In the mark_reserved_regions_for_nid() code, we attempt to reserve the area for a node before we have allocated the NODE_DATA() for that nid. We do this since I reordered that loop. I suck. This is causing crashes at bootup on some systems, as reported by Jon Tollefson. This may only present on some systems that have 16GB pages reserved. But, it can probably happen on any system that is trying to reserve large swaths of memory that happen to span other nodes' contents. This commit ensures that we do not touch bootmem for any node which has not been initialized, and also removes a compile warning about an unused variable. Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'lib/string.c')
0 files changed, 0 insertions, 0 deletions