kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, stable@vger.kernel.org
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH stable-4.19 0/2] KVM: nVMX: guest reset fixes
Date: Thu, 25 Jul 2019 13:24:26 +0200	[thread overview]
Message-ID: <b0ca6477-ac1e-bf92-3e3a-902243707f54@redhat.com> (raw)
In-Reply-To: <20190725104645.30642-1-vkuznets@redhat.com>

On 25/07/19 12:46, Vitaly Kuznetsov wrote:
> Few patches were recently marked for stable@ but commits are not
> backportable as-is and require a few tweaks. Here is 4.19 stable backport.
> 
> Jan Kiszka (1):
>   KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested
> 
> Paolo Bonzini (1):
>   KVM: nVMX: do not use dangling shadow VMCS after guest reset
> 
>  arch/x86/kvm/vmx.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks Vitaly for helping out.

Paolo

  parent reply	other threads:[~2019-07-25 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 10:46 [PATCH stable-4.19 0/2] KVM: nVMX: guest reset fixes Vitaly Kuznetsov
2019-07-25 10:46 ` [PATCH stable-4.19 1/2] KVM: nVMX: do not use dangling shadow VMCS after guest reset Vitaly Kuznetsov
2019-07-29  8:58   ` Jack Wang
2019-07-29  9:10     ` Paolo Bonzini
2019-07-29  9:29       ` Jack Wang
2019-07-29  9:30         ` Paolo Bonzini
2019-07-29 15:31           ` Greg Kroah-Hartman
2019-07-25 10:46 ` [PATCH stable-4.19 2/2] KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested Vitaly Kuznetsov
2019-07-25 11:24 ` Paolo Bonzini [this message]
2019-07-26 13:48 ` [PATCH stable-4.19 0/2] KVM: nVMX: guest reset fixes Greg KH

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=b0ca6477-ac1e-bf92-3e3a-902243707f54@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).