This is a note to let you know that I've just added the patch titled
KVM: VMX: avoid guest hang on invalid invvpid instruction
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
kvm-vmx-avoid-guest-hang-on-invalid-invvpid-instruction.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From f6870ee9e53430f2a318ccf0dd5e66bb46194e43 Mon Sep 17 00:00:00 2001
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date: Fri, 18 Mar 2016 16:53:42 +0100
Subject: KVM: VMX: avoid guest hang on invalid invvpid instruction
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
commit f6870ee9e53430f2a318ccf0dd5e66bb46194e43 upstream.
A guest executing an invalid invvpid instruction would hang
because the instruction pointer was not updated.
Reported-by: jmontleo@xxxxxxxxxx
Tested-by: jmontleo@xxxxxxxxxx
Fixes: 99b83ac893b84ed1a62ad6d1f2b6cc32026b9e85
Reviewed-by: David Matlack <dmatlack@xxxxxxxxxx>
Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
arch/x86/kvm/vmx.c | 1 +
1 file changed, 1 insertion(+)
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -7399,6 +7399,7 @@ static int handle_invvpid(struct kvm_vcp
if (!(types & (1UL << type))) {
nested_vmx_failValid(vcpu,
VMXERR_INVALID_OPERAND_TO_INVEPT_INVVPID);
+ skip_emulated_instruction(vcpu);
return 1;
}
Patches currently in stable-queue which might be from pbonzini@xxxxxxxxxx are
queue-4.4/kvm-vmx-fix-nested-vpid-for-old-kvm-guests.patch
queue-4.4/kvm-x86-fix-missed-hardware-breakpoints.patch
queue-4.4/kvm-vmx-avoid-guest-hang-on-invalid-invvpid-instruction.patch
queue-4.4/kvm-i8254-change-pit-discard-tick-policy.patch
queue-4.4/kvm-fix-spin_lock_init-order-on-x86.patch
queue-4.4/kvm-vmx-avoid-guest-hang-on-invalid-invept-instruction.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html