Thomas Gleixner 67f67244f8 x86/kaslr: Fix the vaddr_end mess ... commit 1dddd25125 upstream. vaddr_end for KASLR is only documented in the KASLR code itself and is adjusted depending on config options. So it's not surprising that a change of the memory layout causes KASLR to have the wrong vaddr_end. This can map arbitrary stuff into other areas causing hard to understand problems. Remove the whole ifdef magic and define the start of the cpu_entry_area to be the end of the KASLR vaddr range. Add documentation to that effect. Fixes: 92a0f81d89 ("x86/cpu_entry_area: Move it out of the fixmap") Reported-by: Benjamin Gilbert <benjamin.gilbert@coreos.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Benjamin Gilbert <benjamin.gilbert@coreos.com> Cc: Andy Lutomirski <luto@kernel.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Dave Hansen <dave.hansen@linux.intel.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Garnier <thgarnie@google.com> Cc: Alexander Kuleshov <kuleshovmail@gmail.com> Link: https://lkml.kernel.org/r/alpine.DEB.2.20.1801041320360.1771@nanos Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2018-01-10 09:31:16 +01:00
..
00-INDEX
5level-paging.txt	x86: Enable 5-level paging support via CONFIG_X86_5LEVEL=y	2017-07-21 10:05:19 +02:00
boot-options.txt	x86/mce: Update bootlog description to reflect behavior on AMD	2017-06-14 07:32:10 +02:00
cpu-hotplug-spec
fake-numa-for-cpusets
machinecheck
mm.txt	x86/kaslr: Fix the vaddr_end mess	2018-01-10 09:31:16 +01:00
uefi.txt