Thread (4 messages) 4 messages, 2 authors, 2012-12-20

Re: [PATCH] mm/sparse: don't check return value of alloc_bootmem calls

From: David Rientjes <rientjes@google.com>
Date: 2012-12-20 20:43:58
Also in: lkml

On Thu, 20 Dec 2012, Sasha Levin wrote:
So what we really need is to update the documentation of __alloc_bootmem_node, I'll send
a patch that does that instead.
It panics iff slab is not available to allocate from yet, otherwise it's 
just a wrapper around kmalloc().  This emits a warning to the kernel log, 
though, so __alloc_bootmem_node() should certainly not be called that late 
in the boot sequence.

Since __alloc_bootmem_node_nopanic() is the way to avoid the panic, I 
think the change that should be made here so to panic even when the 
kmalloc() fails in __alloc_bootmem_node(), __alloc_bootmem_node_high(), 
and __alloc_bootmem_low_node().

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help