summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorJames Morse <james.morse@arm.com>2019-01-24 16:32:55 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-03-13 14:03:16 -0700
commitc72b4dcd26795d6941db0cedd2c2212bb9b32d2f (patch)
tree283a4e58d58a7dfcefee8e51954e40daa59470f6 /security
parent2f3317ddcb55b59e66c1629f39063473949ebf99 (diff)
arm64: kprobe: Always blacklist the KVM world-switch code
[ Upstream commit f2b3d8566d81deaca31f4e3163def0bea7746e11 ] On systems with VHE the kernel and KVM's world-switch code run at the same exception level. Code that is only used on a VHE system does not need to be annotated as __hyp_text as it can reside anywhere in the kernel text. __hyp_text was also used to prevent kprobes from patching breakpoint instructions into this region, as this code runs at a different exception level. While this is no longer true with VHE, KVM still switches VBAR_EL1, meaning a kprobe's breakpoint executed in the world-switch code will cause a hyp-panic. Move the __hyp_text check in the kprobes blacklist so it applies on VHE systems too, to cover the common code and guest enter/exit assembly. Fixes: 888b3c8720e0 ("arm64: Treat all entry code as non-kprobe-able") Reviewed-by: Christoffer Dall <christoffer.dall@arm.com> Signed-off-by: James Morse <james.morse@arm.com> Acked-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions