aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm64/Kconfig
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2019-11-08 17:12:43 +0000
committerCatalin Marinas <catalin.marinas@arm.com>2019-11-08 17:36:48 +0000
commit294a9ddde6cdbf931a28b8c8c928d3f799b61cb5 (patch)
treec7c0c96500a850e4957ae66d71fbda68ef1d1ae1 /arch/arm64/Kconfig
parentLinux 5.4-rc3 (diff)
downloadlinux-dev-294a9ddde6cdbf931a28b8c8c928d3f799b61cb5.tar.xz
linux-dev-294a9ddde6cdbf931a28b8c8c928d3f799b61cb5.zip
arm64: kaslr: Announce KASLR status on boot
Currently the KASLR code is silent at boot unless it forces on KPTI in which case a message will be printed for that. This can lead to users incorrectly believing their system has the feature enabled when it in fact does not, and if they notice the problem the lack of any diagnostics makes it harder to understand the problem. Add an initcall which prints a message showing the status of KASLR during boot to make the status clear. This is particularly useful in cases where we don't have a seed. It seems to be a relatively common error for system integrators and administrators to enable KASLR in their configuration but not provide the seed at runtime, often due to seed provisioning breaking at some later point after it is initially enabled and verified. Signed-off-by: Mark Brown <broonie@kernel.org> Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm64/Kconfig')
0 files changed, 0 insertions, 0 deletions