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

commit 861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a upstream.

'__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] 517e1fbeb6: 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: dc16ecf7fd ("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>
Signed-off-by: Willy Tarreau <w@1wt.eu>

This commit is contained in:

Laura Abbott

2017-05-08 14:23:16 -07:00

committed by

syphyr

parent 60de168ef7

commit 249d07ea20

1 changed files with 1 additions and 0 deletions

									
										1

arch/x86/mm/numa_32.c

										View File
									
				@ -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();

				}

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

1 arch/x86/mm/numa_32.c Unescape Escape View File

1

arch/x86/mm/numa_32.c

View File