KVM: MMU: handle invalid root_hpa at __direct_map
authorMarcelo Tosatti <mtosatti@redhat.com>
Thu, 19 Dec 2013 17:28:51 +0000 (15:28 -0200)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 20 Dec 2013 18:22:49 +0000 (19:22 +0100)
commit989c6b34f6a9480e397b170cc62237e89bf4fdb9
tree2c0336c3ead7c6378e0c25744df50f777bfd4098
parent4c4d563b49830a66537c3f51070dad74d7a81d3a
KVM: MMU: handle invalid root_hpa at __direct_map

It is possible for __direct_map to be called on invalid root_hpa
(-1), two examples:

1) try_async_pf -> can_do_async_pf
    -> vmx_interrupt_allowed -> nested_vmx_vmexit
2) vmx_handle_exit -> vmx_interrupt_allowed -> nested_vmx_vmexit

Then to load_vmcs12_host_state and kvm_mmu_reset_context.

Check for this possibility, let fault exception be regenerated.

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=924916

Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/mmu.c