diff options
author | Will Deacon <will@kernel.org> | 2020-09-30 11:24:42 +0100 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2020-10-02 09:25:25 +0100 |
commit | ffd1b63a5860968068e943eab33383a766d30f64 (patch) | |
tree | 3b2450a4440c5d83fd1335df552a0ca69b4e5ee5 /Documentation/virt | |
parent | b259d137e91d80bf92eac453ffab179eb7941ede (diff) | |
download | linux-ffd1b63a5860968068e943eab33383a766d30f64.tar.bz2 |
KVM: arm64: Ensure user_mem_abort() return value is initialised
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.
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Will Deacon <will@kernel.org>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
Cc: Gavin Shan <gshan@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>
Link: https://lore.kernel.org/r/20200930102442.16142-1-will@kernel.org
Diffstat (limited to 'Documentation/virt')
0 files changed, 0 insertions, 0 deletions