1dddd25125
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:
|
||
---|---|---|
.. | ||
00-INDEX | ||
5level-paging.txt | ||
boot-options.txt | ||
cpu-hotplug-spec | ||
fake-numa-for-cpusets | ||
machinecheck | ||
mm.txt | ||
uefi.txt |