On Fri, Jun 15, 2018 at 2:16 PM, Krish Sadhukhan <krish.sadhukhan@xxxxxxxxxx> wrote: > > > On 06/15/2018 01:36 PM, Marc Orr wrote: >> >> This patch extends the checks done prior to a nested VM entry. >> Specifically, it extends the check_vmentry_prereqs function with checks >> for fields relevant to the VM-entry event injection information, as >> described in the Intel SDM, volume 3. >> >> This patch is motivated by a syzkaller bug, where a bad VM-entry >> interruption information field is generated in the VMCS02, which causes >> the nested VM launch to fail. Then, KVM fails to resume L1. >> >> While KVM should be improved to correctly resume L1 execution after a >> failed nested launch, this change is justified because the existing code >> to resume L1 is flaky/ad-hoc and the test coverage for resuming L1 is >> sparse. >> >> Reported-by: syzbot <syzkaller@xxxxxxxxxxxxxxxx> >> Signed-off-by: Marc Orr <marcorr@xxxxxxxxxx> > Reviewed-by: Krish Sadhukhan <krish.sadhukhan@xxxxxxxxxx> Reviewed-by: Jim Mattson <jmattson@xxxxxxxxxx>
