From: <gregkh@linuxfoundation.org>
To: pbonzini@redhat.com, dmatlack@google.com, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "KVM: VMX: avoid guest hang on invalid invept instruction" has been added to the 4.4-stable tree
Date: Sat, 09 Apr 2016 11:30:23 -0700 [thread overview]
Message-ID: <1460226623247209@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
KVM: VMX: avoid guest hang on invalid invept 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-invept-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@vger.kernel.org> know about it.
>From 2849eb4f99d54925c543db12917127f88b3c38ff Mon Sep 17 00:00:00 2001
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Fri, 18 Mar 2016 16:53:29 +0100
Subject: KVM: VMX: avoid guest hang on invalid invept instruction
From: Paolo Bonzini <pbonzini@redhat.com>
commit 2849eb4f99d54925c543db12917127f88b3c38ff upstream.
A guest executing an invalid invept instruction would hang
because the instruction pointer was not updated.
Fixes: bfd0a56b90005f8c8a004baf407ad90045c2b11e
Reviewed-by: David Matlack <dmatlack@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
arch/x86/kvm/vmx.c | 1 +
1 file changed, 1 insertion(+)
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -7340,6 +7340,7 @@ static int handle_invept(struct kvm_vcpu
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@redhat.com 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
reply other threads:[~2016-04-09 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460226623247209@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmatlack@google.com \
--cc=pbonzini@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox