All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH stable-5.1 0/3] KVM: x86: FPU and nested VMX guest reset fixes
Date: Fri, 26 Jul 2019 15:49:44 +0200	[thread overview]
Message-ID: <20190726134944.GC23085@kroah.com> (raw)
In-Reply-To: <20190725114938.3976-1-vkuznets@redhat.com>

On Thu, Jul 25, 2019 at 01:49:35PM +0200, Vitaly Kuznetsov wrote:
> Few patches were recently marked for stable@ but commits are not
> backportable as-is and require a few tweaks. Here is 5.1 stable backport.
> 
> [PATCH2 of the series applies as-is, I have it here for completeness]
> 
> Jan Kiszka (1):
>   KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested
> 
> Paolo Bonzini (2):
>   KVM: nVMX: do not use dangling shadow VMCS after guest reset
>   Revert "kvm: x86: Use task structs fpu field for user"

All now applied, thanks!

greg k-h

      parent reply	other threads:[~2019-07-26 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 11:49 [PATCH stable-5.1 0/3] KVM: x86: FPU and nested VMX guest reset fixes Vitaly Kuznetsov
2019-07-25 11:49 ` [PATCH stable-5.1 1/3] KVM: nVMX: do not use dangling shadow VMCS after guest reset Vitaly Kuznetsov
2019-07-25 11:49 ` [PATCH stable-5.1 2/3] KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested Vitaly Kuznetsov
2019-07-25 11:49 ` [PATCH stable-5.1 3/3] Revert "kvm: x86: Use task structs fpu field for user" Vitaly Kuznetsov
2019-07-25 15:48 ` [PATCH stable-5.1 0/3] KVM: x86: FPU and nested VMX guest reset fixes Paolo Bonzini
2019-07-26 13:49 ` Greg KH [this message]

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=20190726134944.GC23085@kroah.com \
    --to=greg@kroah.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.