Commit 861ce4a3 authored May 08, 2017 by Laura Abbott Committed by Ingo Molnar May 09, 2017

x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init()



'__vmalloc_start_set' currently only gets set in initmem_init() when
!CONFIG_NEED_MULTIPLE_NODES. This breaks detection of vmalloc address
with virt_addr_valid() with CONFIG_NEED_MULTIPLE_NODES=y, causing
a kernel crash:

  [mm/usercopy] 517e1fbe: kernel BUG at arch/x86/mm/physaddr.c:78!

Set '__vmalloc_start_set' appropriately for that case as well.

Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Fixes: dc16ecf7 ("x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid")
Link: http://lkml.kernel.org/r/1494278596-30373-1-git-send-email-labbott@redhat.com


Signed-off-by: Ingo Molnar <mingo@kernel.org>

parent 8638100c

arch/x86/mm/numa_32.c

+1 −0

Original line number	Diff line number	Diff line
		@@ -100,5 +100,6 @@ void __init initmem_init(void)
		printk(KERN_DEBUG "High memory starts at vaddr %08lx\n",
		(ulong) pfn_to_kaddr(highstart_pfn));

		__vmalloc_start_set = true;
		setup_bootmem_allocator();
		}

Admin message