diff options
author | Ard Biesheuvel <[email protected]> | 2020-10-14 10:18:57 +0200 |
---|---|---|
committer | Catalin Marinas <[email protected]> | 2020-11-10 18:43:25 +0000 |
commit | 97d6786e0669daa5c2f2d07a057f574e849dfd3e (patch) | |
tree | ca40963bca9a000bef2d29806022494dd7a1d2c6 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | f8394f232b1eab649ce2df5c5f15b0e528c92091 (diff) |
arm64: mm: account for hotplug memory when randomizing the linear region
As a hardening measure, we currently randomize the placement of
physical memory inside the linear region when KASLR is in effect.
Since the random offset at which to place the available physical
memory inside the linear region is chosen early at boot, it is
based on the memblock description of memory, which does not cover
hotplug memory. The consequence of this is that the randomization
offset may be chosen such that any hotplugged memory located above
memblock_end_of_DRAM() that appears later is pushed off the end of
the linear region, where it cannot be accessed.
So let's limit this randomization of the linear region to ensure
that this can no longer happen, by using the CPU's addressable PA
range instead. As it is guaranteed that no hotpluggable memory will
appear that falls outside of that range, we can safely put this PA
range sized window anywhere in the linear region.
Signed-off-by: Ard Biesheuvel <[email protected]>
Cc: Anshuman Khandual <[email protected]>
Cc: Will Deacon <[email protected]>
Cc: Steven Price <[email protected]>
Cc: Robin Murphy <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Catalin Marinas <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions