diff options
author | Sean Christopherson <[email protected]> | 2023-07-21 13:18:59 -0700 |
---|---|---|
committer | Sean Christopherson <[email protected]> | 2023-08-03 15:37:15 -0700 |
commit | a788fbb763b5001f67f2ecdf207a357f9b12838f (patch) | |
tree | 7574d983e07db0cd9b8fab1dcb88a2c97661157b /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | 2e6b9bd49b702c4a52278e35202354b709021116 (diff) |
KVM: VMX: Skip VMCLEAR logic during emergency reboots if CR4.VMXE=0
Bail from vmx_emergency_disable() without processing the list of loaded
VMCSes if CR4.VMXE=0, i.e. if the CPU can't be post-VMXON. It should be
impossible for the list to have entries if VMX is already disabled, and
even if that invariant doesn't hold, VMCLEAR will #UD anyways, i.e.
processing the list is pointless even if it somehow isn't empty.
Assuming no existing KVM bugs, this should be a glorified nop. The
primary motivation for the change is to avoid having code that looks like
it does VMCLEAR, but then skips VMXON, which is nonsensical.
Suggested-by: Kai Huang <[email protected]>
Reviewed-by: Kai Huang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions