Re: [PATCH v2] KVM: nVMX: do not use dangling shadow VMCS after guest reset

> On 20 Jul 2019, at 1:21, Paolo Bonzini wrote: > > On 20/07/19 00:06, Liran Alon wrote: >> >> >>> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote: >>> >>> If a KVM guest is reset while running a nested guest, free_nested will >>> disable the shadow VMCS execution control in the vmcs01. Howe

Re: [PATCH v2] KVM: nVMX: do not use dangling shadow VMCS after guest reset

On 20/07/19 00:06, Liran Alon wrote: > > >> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote: >> >> If a KVM guest is reset while running a nested guest, free_nested will >> disable the shadow VMCS execution control in the vmcs01. However, >> on the next KVM_RUN vmx_vcpu_run would nevertheless try

Re: [PATCH v2] KVM: nVMX: do not use dangling shadow VMCS after guest reset

> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote: > > If a KVM guest is reset while running a nested guest, free_nested will > disable the shadow VMCS execution control in the vmcs01. However, > on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync > the VMCS12 to the shadow VMCS whic

[PATCH v2] KVM: nVMX: do not use dangling shadow VMCS after guest reset

If a KVM guest is reset while running a nested guest, free_nested will disable the shadow VMCS execution control in the vmcs01. However, on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync the VMCS12 to the shadow VMCS which has since been freed. This causes a vmptrld of a NULL pointe