* Re: [PATCH] KVM: arm64: Ensure user_mem_abort() return value is initialised
[not found] <20200930102442.16142-1-will@kernel.org>
@ 2020-10-02 8:20 ` Marc Zyngier
0 siblings, 0 replies; only message in thread
From: Marc Zyngier @ 2020-10-02 8:20 UTC (permalink / raw)
To: kvmarm, David Brazdil, Will Deacon
Cc: linux-arm-kernel, linux-kernel, Dennis Zhou, Catalin Marinas,
Tejun Heo, kernel-team, Christoph Lameter, kernel test robot,
Will Deacon, Dan Carpenter
On Wed, 30 Sep 2020 11:24:42 +0100, Will Deacon wrote:
> If a change in the MMU notifier sequence number forces user_mem_abort()
> to return early when attempting to handle a stage-2 fault, we return
> uninitialised stack to kvm_handle_guest_abort(), which could potentially
> result in the injection of an external abort into the guest or a spurious
> return to userspace. Neither or these are what we want to do.
>
> Initialise 'ret' to 0 in user_mem_abort() so that bailing due to a
> change in the MMU notrifier sequence number is treated as though the
> fault was handled.
Applied to next, thanks!
[1/1] KVM: arm64: Ensure user_mem_abort() return value is initialised
commit: 84cd7df693f07df94d617049773f7c757a2b7847
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-10-02 8:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20200930102442.16142-1-will@kernel.org>
2020-10-02 8:20 ` [PATCH] KVM: arm64: Ensure user_mem_abort() return value is initialised Marc Zyngier
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).