arm64: permit KASLR in linear region even VArange == PArange
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | arm64: simplify rules for defining ARM64_MEMSTART_ALIGNarch/ | +4 | 0 replies | |
| 2/2 | arm64: kaslr: take free space at start of DRAM into accountarch/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] arm64: permit KASLR in linear region even VArange == PArange
Kefeng reports in [0] that using PArange to size the randomized linear region offset leads to cases where randomization is no longer possible even if the actual placement of DRAM in memory would otherwise have permitted it.
Instead of using CONFIG_MEMORY_HOTPLUG to choose at build time between to different behaviors in this regard, let's try addressing this by reducing the minimum relative aligment between VA and PA in the linear region, and taking advantage of the space at the base of physical memory below the first memblock to permit some randomization of the placement of physical DRAM in the virtual address map.
[0] https://lore.kernel.org/linux-arm-kernel/[email protected]/
Ard Biesheuvel (2):
arm64: simplify rules for defining ARM64_MEMSTART_ALIGN
arm64: kaslr: take free space at start of DRAM into account
arch/arm64/include/asm/kernel-pgtable.h | 27 +++----------------- arch/arm64/mm/init.c | 3 ++- 2 files changed, 6 insertions(+), 24 deletions(-)
Signature · 7 lines
2.30.2 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel