KVM: selftests: Remove x86's so called "MMIO warning" test
authorSean Christopherson <seanjc@google.com>
Tue, 15 Aug 2023 22:00:30 +0000 (15:00 -0700)
committerSean Christopherson <seanjc@google.com>
Wed, 29 Nov 2023 22:53:29 +0000 (14:53 -0800)
commite29f5d0c3c7c055b36ef55f9e92100450b2506a3
tree2ef0a8a4c07309877abca08d58dc3b70db8498ad
parent1b78d474ce4ecbf15a4a8b08994b8ed8ceec0dab
KVM: selftests: Remove x86's so called "MMIO warning" test

Remove x86's mmio_warning_test, as it is unnecessarily complex (there's no
reason to fork, spawn threads, initialize srand(), etc..), unnecessarily
restrictive (triggering triple fault is not unique to Intel CPUs without
unrestricted guest), and provides no meaningful coverage beyond what
basic fuzzing can achieve (running a vCPU with garbage is fuzzing's bread
and butter).

That the test has *all* of the above flaws is not coincidental, as the
code was copy+pasted almost verbatim from the syzkaller reproducer that
originally found the KVM bug (which has long since been fixed).

Cc: Michal Luczaj <mhal@rbox.co>
Link: https://groups.google.com/g/syzkaller/c/lHfau8E3SOE
Link: https://lore.kernel.org/r/20230815220030.560372-1-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
tools/testing/selftests/kvm/Makefile
tools/testing/selftests/kvm/x86_64/mmio_warning_test.c [deleted file]