From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Jack Wang" <jack.wang.usish@gmail.com>,
"Sasha Levin" <sashal@kernel.org>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
stable@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH stable-4.19 1/2] KVM: nVMX: do not use dangling shadow VMCS after guest reset
Date: Mon, 29 Jul 2019 17:31:41 +0200 [thread overview]
Message-ID: <20190729153141.GA9692@kroah.com> (raw)
In-Reply-To: <471a1023-4f0a-5727-e7b2-48701f75188f@redhat.com>
On Mon, Jul 29, 2019 at 11:30:19AM +0200, Paolo Bonzini wrote:
> On 29/07/19 11:29, Jack Wang wrote:
> > Thanks Paolo for confirmation. I'm asking because we had one incident
> > in our production with 4.14.129 kernel,
> > System is Skylake Gold cpu, first kvm errors, host hung afterwards
> >
> > kernel: [1186161.091160] kvm: vmptrld (null)/6bfc00000000 failed
> > kernel: [1186161.091537] kvm: vmclear fail: (null)/6bfc00000000
> > kernel: [1186186.490300] watchdog: BUG: soft lockup - CPU#54 stuck for
> > 23s! [qemu:16639]
> >
> > Hi Sasha, hi Greg,
> >
> > Would be great if you can pick this patch also to 4.14 kernel.
>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Ok, now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2019-07-29 15:31 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 [this message]
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 ` [PATCH stable-4.19 0/2] KVM: nVMX: guest reset fixes Paolo Bonzini
2019-07-26 13:48 ` 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=20190729153141.GA9692@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jack.wang.usish@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sashal@kernel.org \
--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.