[<prev] [next>] [day] [month] [year] [list]
Message-Id: <160162675379.1930042.16468950598631893927.b4-ty@kernel.org>
Date: Fri, 2 Oct 2020 09:20:00 +0100
From: Marc Zyngier <maz@...nel.org>
To: kvmarm@...ts.cs.columbia.edu, David Brazdil <dbrazdil@...gle.com>,
Will Deacon <will@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Dennis Zhou <dennis@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Tejun Heo <tj@...nel.org>, kernel-team@...roid.com,
Christoph Lameter <cl@...ux.com>,
kernel test robot <lkp@...el.com>,
Will Deacon <willdeacon@...gle.com>,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH] KVM: arm64: Ensure user_mem_abort() return value is initialised
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.
Powered by blists - more mailing lists