android_kernel_samsung_msm8976/arch/x86/mm
Laura Abbott 249d07ea20 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>
2019-07-27 21:44:34 +02:00
..
kmemcheck
amdtopology.c
dump_pagetables.c
extable.c
fault.c
gup.c
highmem_32.c
hugetlbpage.c mm: larger stack guard gap, between vmas 2017-07-11 00:00:39 +00:00
init.c mm: Tighten x86 /dev/mem with zeroing reads 2017-05-05 19:20:37 +00:00
init_32.c Merge remote-tracking branch 'f2fs/linux-3.10.y' into HEAD 2017-04-18 17:02:28 +02:00
init_64.c Merge remote-tracking branch 'f2fs/linux-3.10.y' into HEAD 2017-04-18 17:02:28 +02:00
iomap_32.c
ioremap.c
kasan_init_64.c
kmmio.c
Makefile
mm_internal.h
mmap.c UPSTREAM: x86/mm/32: Enable full randomization on i386 and X86_32 2017-10-19 01:00:49 +02:00
mmio-mod.c
numa.c
numa_32.c x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init() 2019-07-27 21:44:34 +02:00
numa_64.c
numa_emulation.c
numa_internal.h
pageattr-test.c
pageattr.c
pat.c
pat_internal.h
pat_rbtree.c
pf_in.c
pf_in.h
pgtable.c
pgtable_32.c
physaddr.c
physaddr.h
setup_nx.c
srat.c
testmmiotrace.c
tlb.c