KVM: x86: Don't report guest userspace emulation error to userspace
authorNadav Amit <namit@cs.technion.ac.il>
Tue, 16 Sep 2014 23:50:50 +0000 (02:50 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 21 Nov 2014 17:22:55 +0000 (09:22 -0800)
commitc75f394964bc21d0b890bd62ead90ff51b3e1e72
treef94423db5aed3470669a96813c1db19191677832
parent2e4ce498811f1aa2e9f2e600d442ad8da0ab6534
KVM: x86: Don't report guest userspace emulation error to userspace

commit a2b9e6c1a35afcc0973acb72e591c714e78885ff upstream.

Commit fc3a9157d314 ("KVM: X86: Don't report L2 emulation failures to
user-space") disabled the reporting of L2 (nested guest) emulation failures to
userspace due to race-condition between a vmexit and the instruction emulator.
The same rational applies also to userspace applications that are permitted by
the guest OS to access MMIO area or perform PIO.

This patch extends the current behavior - of injecting a #UD instead of
reporting it to userspace - also for guest userspace code.

Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/x86/kvm/x86.c