From: James Morse <james.morse@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Christoffer Dall <christoffer.dall@arm.com>,
james.morse@arm.com, Masami Hiramatsu <mhiramat@kernel.org>,
kvmarm@lists.cs.columbia.edu
Subject: [PATCH v2 0/4] Fix some KVM/HYP interactions with kprobes
Date: Thu, 24 Jan 2019 16:32:53 +0000 [thread overview]
Message-ID: <20190124163257.233929-1-james.morse@arm.com> (raw)
Hi guys,
When looking at Masami Hiramatsu's kprobe cleanup series, it occurred
to me the 'no KVM' isn't just about the EL1/EL2 split on non-VHE systems,
but whether KVM is prepared to handle stepping on a breakpoint. It's not.
This labels all the VHE-only KVM functions that run during world switch
with NOKPROBE_SYMBOL(), and always blacklists __hyp_text for kprobes
to cover the common guest entry/exit code.
I anticipate patch 1 going via the KVM tree to avoid conflicts.
Patch 2 will conflict with [0].
I'm not sure what the best thing to do with the hyp-stub is.
Patch 3 moves it to __hyp_text, and patch 4 covers the hibernate fallout
from doing that. We don't have any other mmu-off but not idmap'd text.
Probing the hyp-stub has to be done by address as the symbol names
alias those in the __entry_text, which is blacklisted. (although this
might depend on link order). I think anyone doing this is trying to
shoot themselves in the foot.
Know issues:
* Other regions we should blacklist are the kexec and hibernate 'copy
everything' code, as the vectors may have been overwritten by the time
we step on the probe. cpu-suspend needs investigating...
Thanks,
James
[0] lore.kernel.org/r/154753341900.31541.8135985235882849464.stgit@devbox
James Morse (4):
KVM: arm64: Forbid kprobing of the VHE world-switch code
arm64: kprobe: Always blacklist the KVM world-switch code
arm64: hyp-stub: Forbid kprobing of the hyp-stub
arm64: hibernate: Clean the __hyp_text to PoC after resume
arch/arm64/kernel/hibernate.c | 4 +++-
arch/arm64/kernel/hyp-stub.S | 2 ++
arch/arm64/kernel/probes/kprobes.c | 6 +++---
arch/arm64/kvm/hyp/switch.c | 5 +++++
arch/arm64/kvm/hyp/sysreg-sr.c | 5 +++++
5 files changed, 18 insertions(+), 4 deletions(-)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-01-24 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 16:32 James Morse [this message]
2019-01-24 16:32 ` [PATCH v2 1/4] KVM: arm64: Forbid kprobing of the VHE world-switch code James Morse
2019-01-25 1:28 ` Masami Hiramatsu
2019-01-31 8:08 ` Christoffer Dall
2019-01-31 18:53 ` James Morse
2019-02-01 8:04 ` Christoffer Dall
2019-02-01 13:34 ` Marc Zyngier
2019-01-24 16:32 ` [PATCH v2 2/4] arm64: kprobe: Always blacklist the KVM " James Morse
2019-01-31 8:08 ` Christoffer Dall
2019-01-24 16:32 ` [PATCH v2 3/4] arm64: hyp-stub: Forbid kprobing of the hyp-stub James Morse
2019-01-31 8:04 ` Christoffer Dall
2019-02-01 12:02 ` James Morse
2019-01-24 16:32 ` [PATCH v2 4/4] arm64: hibernate: Clean the __hyp_text to PoC after resume James Morse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190124163257.233929-1-james.morse@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mhiramat@kernel.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).