diff options
| author | Laura Abbott <labbott@redhat.com> | 2017-05-08 14:23:16 -0700 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2017-05-09 08:12:27 +0200 |
| commit | 861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a (patch) | |
| tree | 9e6172bffc59dd5697a7227d5311e1e811ad77af /arch | |
| parent | 8638100c52bb7782462b14aad102a4aaf0c7094c (diff) | |
| download | linux-861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a.tar.gz linux-861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a.tar.bz2 linux-861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a.zip | |
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] 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: dc16ecf7fd1f ("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>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/x86/mm/numa_32.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/x86/mm/numa_32.c b/arch/x86/mm/numa_32.c index 6b7ce6279133..aca6295350f3 100644 --- a/arch/x86/mm/numa_32.c +++ b/arch/x86/mm/numa_32.c @@ -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(); } |