From: James Morse <james.morse@arm.com> To: Christoffer Dall <christoffer.dall@arm.com> Cc: Marc Zyngier <marc.zyngier@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Masami Hiramatsu <mhiramat@kernel.org>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 3/4] arm64: hyp-stub: Forbid kprobing of the hyp-stub Date: Fri, 1 Feb 2019 12:02:08 +0000 [thread overview] Message-ID: <195916cb-03ac-6d83-03a8-e09fec90b247@arm.com> (raw) In-Reply-To: <20190131080421.GJ13482@e113682-lin.lund.arm.com> Hi Christoffer, On 31/01/2019 08:04, Christoffer Dall wrote: > On Thu, Jan 24, 2019 at 04:32:56PM +0000, James Morse wrote: >> The hyp-stub is loaded by the kernel's early startup code at EL2 >> during boot, before KVM takes ownership later. The hyp-stub's >> text is part of the regular kernel text, meaning it can be kprobed. >> >> A breakpoint in the hyp-stub causes the CPU to spin in el2_sync_invalid. >> >> Add it to the __hyp_text. >> This has been a problem since kprobes was merged, it should >> probably have been covered in 888b3c8720e0. >> >> I'm not sure __hyp_text is the right place. Its not idmaped, >> and as it contains a set of vectors, adding it to the host/hyp >> idmap sections could grow them beyond a page... but it does >> run with the MMU off, so does need to be cleaned to PoC when >> anything wacky, like hibernate happens. With this patch, >> hibernate should clean the __hyp_text to PoC too. > > How did this code get cleaned before? It didn't need to be cleaned as KVM executes it with the MMU on. KVM's MMU-off code lives in the hyp_idmap, which is cleaned. (as is the kernel's idmap). The hibernate-cache-cleaning was trying to do the absolute minimum, but the hyp-stub got forgotten. > Is there a problem you can identify with putting it in __hyp_text? > Seems to me we should just stick it there if it has no negative > side-effects and otherwise we have to make up a separate section with a > specialized meaning. Yup, there is no problem with the extra cache-maintenance. The hyp-stub is the odd one out, its runtime code that runs with the MMU off, but isn't idmaped. I wasn't sure if we wanted to create some special section.(having to name it is a good enough reason not to!) Thanks, James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com> To: Christoffer Dall <christoffer.dall@arm.com> Cc: Marc Zyngier <marc.zyngier@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Masami Hiramatsu <mhiramat@kernel.org>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 3/4] arm64: hyp-stub: Forbid kprobing of the hyp-stub Date: Fri, 1 Feb 2019 12:02:08 +0000 [thread overview] Message-ID: <195916cb-03ac-6d83-03a8-e09fec90b247@arm.com> (raw) In-Reply-To: <20190131080421.GJ13482@e113682-lin.lund.arm.com> Hi Christoffer, On 31/01/2019 08:04, Christoffer Dall wrote: > On Thu, Jan 24, 2019 at 04:32:56PM +0000, James Morse wrote: >> The hyp-stub is loaded by the kernel's early startup code at EL2 >> during boot, before KVM takes ownership later. The hyp-stub's >> text is part of the regular kernel text, meaning it can be kprobed. >> >> A breakpoint in the hyp-stub causes the CPU to spin in el2_sync_invalid. >> >> Add it to the __hyp_text. >> This has been a problem since kprobes was merged, it should >> probably have been covered in 888b3c8720e0. >> >> I'm not sure __hyp_text is the right place. Its not idmaped, >> and as it contains a set of vectors, adding it to the host/hyp >> idmap sections could grow them beyond a page... but it does >> run with the MMU off, so does need to be cleaned to PoC when >> anything wacky, like hibernate happens. With this patch, >> hibernate should clean the __hyp_text to PoC too. > > How did this code get cleaned before? It didn't need to be cleaned as KVM executes it with the MMU on. KVM's MMU-off code lives in the hyp_idmap, which is cleaned. (as is the kernel's idmap). The hibernate-cache-cleaning was trying to do the absolute minimum, but the hyp-stub got forgotten. > Is there a problem you can identify with putting it in __hyp_text? > Seems to me we should just stick it there if it has no negative > side-effects and otherwise we have to make up a separate section with a > specialized meaning. Yup, there is no problem with the extra cache-maintenance. The hyp-stub is the odd one out, its runtime code that runs with the MMU off, but isn't idmaped. I wasn't sure if we wanted to create some special section.(having to name it is a good enough reason not to!) Thanks, James _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-01 12:02 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-24 16:32 [PATCH v2 0/4] Fix some KVM/HYP interactions with kprobes James Morse 2019-01-24 16:32 ` James Morse 2019-01-24 16:32 ` [PATCH v2 1/4] KVM: arm64: Forbid kprobing of the VHE world-switch code James Morse 2019-01-24 16:32 ` James Morse 2019-01-25 1:28 ` Masami Hiramatsu 2019-01-25 1:28 ` Masami Hiramatsu 2019-01-31 8:08 ` Christoffer Dall 2019-01-31 8:08 ` Christoffer Dall 2019-01-31 18:53 ` James Morse 2019-01-31 18:53 ` James Morse 2019-02-01 8:04 ` Christoffer Dall 2019-02-01 8:04 ` Christoffer Dall 2019-02-01 13:34 ` Marc Zyngier 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-24 16:32 ` James Morse 2019-01-31 8:08 ` Christoffer Dall 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-24 16:32 ` James Morse 2019-01-31 8:04 ` Christoffer Dall 2019-01-31 8:04 ` Christoffer Dall 2019-02-01 12:02 ` James Morse [this message] 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 2019-01-24 16:32 ` 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=195916cb-03ac-6d83-03a8-e09fec90b247@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.