path: root/arch/x86/kvm/vmx/nested.c
diff options
authorSean Christopherson <>2021-08-11 21:56:15 -0700
committerPaolo Bonzini <>2021-08-13 03:20:58 -0400
commit18712c13709d2de9516c5d3414f707c4f0a9c190 (patch)
tree2bebad657a2c375cf88c47d1a8900c5f5efe17da /arch/x86/kvm/vmx/nested.c
parent85aa8889b82e0eec680a21ea28dbf57c6acfe182 (diff)
KVM: nVMX: Use vmx_need_pf_intercept() when deciding if L0 wants a #PF
Use vmx_need_pf_intercept() when determining if L0 wants to handle a #PF in L2 or if the VM-Exit should be forwarded to L1. The current logic fails to account for the case where #PF is intercepted to handle guest.MAXPHYADDR < host.MAXPHYADDR and ends up reflecting all #PFs into L1. At best, L1 will complain and inject the #PF back into L2. At worst, L1 will eat the unexpected fault and cause L2 to hang on infinite page faults. Note, while the bug was technically introduced by the commit that added support for the MAXPHYADDR madness, the shame is all on commit a0c134347baf ("KVM: VMX: introduce vmx_need_pf_intercept"). Fixes: 1dbf5d68af6f ("KVM: VMX: Add guest physical address check in EPT violation and misconfig") Cc: Cc: Peter Shier <> Cc: Oliver Upton <> Cc: Jim Mattson <> Signed-off-by: Sean Christopherson <> Message-Id: <> Signed-off-by: Paolo Bonzini <>
Diffstat (limited to 'arch/x86/kvm/vmx/nested.c')
1 files changed, 2 insertions, 1 deletions
diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
index 81160ebe6acb..b3f77d18eb5a 100644
--- a/arch/x86/kvm/vmx/nested.c
+++ b/arch/x86/kvm/vmx/nested.c
@@ -5855,7 +5855,8 @@ static bool nested_vmx_l0_wants_exit(struct kvm_vcpu *vcpu,
if (is_nmi(intr_info))
return true;
else if (is_page_fault(intr_info))
- return vcpu->arch.apf.host_apf_flags || !enable_ept;
+ return vcpu->arch.apf.host_apf_flags ||
+ vmx_need_pf_intercept(vcpu);
else if (is_debug(intr_info) &&
vcpu->guest_debug &