Chris Metcalf 1b4ace4141 bootmem: avoid freeing to bootmem after bootmem is done
Bootmem isn't popular any more, but some architectures still use it, and
freeing to bootmem after calling free_all_bootmem_core() can end up
scribbling over random memory.  Instead, make sure the kernel generates
a warning in this case by ensuring the node_bootmem_map field is
non-NULL when are freeing or marking bootmem.

An instance of this bug was just fixed in the tile architecture ("tile:
use free_bootmem_late() for initrd") and catching this case more widely
seems like a good thing.

Signed-off-by: Chris Metcalf <cmetcalf@ezchip.com>
Acked-by: Mel Gorman <mgorman@suse.de>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Paul McQuade <paulmcquad@gmail.com>
Cc: Tang Chen <tangchen@cn.fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2015-09-08 15:35:28 -07:00
..
2015-06-24 17:49:45 -07:00
2015-09-08 15:35:28 -07:00
2015-04-15 16:35:18 -07:00
2015-09-08 15:35:28 -07:00
2015-02-11 17:06:02 -08:00
2015-09-04 16:54:41 -07:00
2015-09-08 15:35:28 -07:00
2015-09-08 15:35:28 -07:00
2015-06-25 17:00:37 -07:00
2015-06-25 17:00:37 -07:00
2015-06-25 17:00:37 -07:00
2015-06-25 17:00:37 -07:00