Revision 0447378a4a793da008451fad50bc0f93e9675ae6 authored by Marc Orr on 21 June 2018, 00:21:29 UTC, committed by Radim Krčmář on 22 June 2018, 14:46:26 UTC
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@googlegroups.com> Signed-off-by: Marc Orr <marcorr@google.com> [Removed comment whose parts were describing previous revisions and the rest was obvious from function/variable naming. - Radim] Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
1 parent 5f9077c
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 208 bytes |
Makefile | -rw-r--r-- | 152 bytes |
af_netlink.c | -rw-r--r-- | 64.5 KB |
af_netlink.h | -rw-r--r-- | 1.8 KB |
diag.c | -rw-r--r-- | 5.4 KB |
genetlink.c | -rw-r--r-- | 25.6 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...