diff options
| author | Yinghai Lu <yinghai@kernel.org> | 2012-07-18 00:47:51 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-07-18 01:21:29 +0200 |
| commit | c8f4a2d095bcb7ff798f984b9c7d16b4c8d194c3 (patch) | |
| tree | 9682189dfce619c69ceea4c4d49f2eaa7aeca4b8 /mm/prio_tree.c | |
| parent | Linux 3.5-rc7 (diff) | |
| download | linux-c8f4a2d095bcb7ff798f984b9c7d16b4c8d194c3.tar.xz linux-c8f4a2d095bcb7ff798f984b9c7d16b4c8d194c3.zip | |
bootmem: make ___alloc_bootmem_node_nopanic() really nopanic
In reaction to commit 99ab7b19440a ("mm: sparse: fix usemap allocation
above node descriptor section") Johannes said:
| while backporting the below patch, I realised that your fix busted
| f5bf18fa22f8 again. The problem was not a panicking version on
| allocation failure but when the usemap size was too large such that
| goal + size > limit triggers the BUG_ON in the bootmem allocator. So
| we need a version that passes limit ONLY if the usemap is smaller than
| the section.
after checking the code, the name of ___alloc_bootmem_node_nopanic()
does not reflect the fact.
Make bootmem really not panic.
Hope will kill bootmem sooner.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: <stable@vger.kernel.org> [3.3.x, 3.4.x]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/prio_tree.c')
0 files changed, 0 insertions, 0 deletions