KVM: nVMX: vmread should not set rflags to specify success in case of #PF
authorMiaohe Lin <linmiaohe@huawei.com>
Sat, 28 Dec 2019 06:25:24 +0000 (14:25 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 14 Feb 2020 21:31:08 +0000 (16:31 -0500)
commit0b414c5489a57789a69bd8be534b5f3ab5cb6d07
tree2c93dc13cee288ed644eb93dd48adc88d3fff246
parentbd350d09215aa30f1197caddceae257cb85bfdba
KVM: nVMX: vmread should not set rflags to specify success in case of #PF

[ Upstream commit a4d956b9390418623ae5d07933e2679c68b6f83c ]

In case writing to vmread destination operand result in a #PF, vmread
should not call nested_vmx_succeed() to set rflags to specify success.
Similar to as done in VMPTRST (See handle_vmptrst()).

Reviewed-by: Liran Alon <liran.alon@oracle.com>
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Cc: stable@vger.kernel.org
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
arch/x86/kvm/vmx.c