KVM: selftests: Extend x86's sync_regs_test to check for event vector races
authorMichal Luczaj <mhal@rbox.co>
Fri, 28 Jul 2023 00:12:58 +0000 (02:12 +0200)
committerSean Christopherson <seanjc@google.com>
Wed, 2 Aug 2023 20:33:20 +0000 (13:33 -0700)
commit60c4063b475215321fc63ab253c9a840bb664f35
tree7296e3c7824133952460147df9b8a596921e66a3
parentae895cbe613a5b193f3953c90c075306bfa4d30b
KVM: selftests: Extend x86's sync_regs_test to check for event vector races

Attempt to modify the to-be-injected exception vector to an illegal value
_after_ the sanity checks performed by KVM_CAP_SYNC_REGS's
arch/x86/kvm/x86.c:kvm_vcpu_ioctl_x86_set_vcpu_events().  Buggy KVM
versions will eventually yells loudly about attempting to inject a bogus
vector, e.g.

  WARNING: CPU: 0 PID: 1107 at arch/x86/kvm/x86.c:547 kvm_check_and_inject_events+0x4a0/0x500 [kvm]

  arch/x86/kvm/x86.c:exception_type():
  WARN_ON(vector > 31 || vector == NMI_VECTOR)

Signed-off-by: Michal Luczaj <mhal@rbox.co>
Link: https://lore.kernel.org/r/20230728001606.2275586-3-mhal@rbox.co
[sean: split to separate patch]
Signed-off-by: Sean Christopherson <seanjc@google.com>
tools/testing/selftests/kvm/x86_64/sync_regs_test.c