From: Sean Christopherson <seanjc@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1] KVM: x86/mmu: Fix an sign-extension bug with mmu_seq that hangs vCPUs
Date: Thu, 24 Aug 2023 06:46:59 -0700 [thread overview]
Message-ID: <ZOdfU1zQ4UCQNVpz@google.com> (raw)
In-Reply-To: <2023082423-ninetieth-hamlet-54dc@gregkh>
On Thu, Aug 24, 2023, Greg Kroah-Hartman wrote:
> On Wed, Aug 23, 2023 at 06:01:04PM -0700, Sean Christopherson wrote:
> > Note, upstream commit ba6e3fe25543 ("KVM: x86/mmu: Grab mmu_invalidate_seq
> > in kvm_faultin_pfn()") unknowingly fixed the bug in v6.3 when refactoring
> > how KVM tracks the sequence counter snapshot.
> >
> > Reported-by: Brian Rak <brak@vultr.com>
> > Reported-by: Amaan Cheval <amaan.cheval@gmail.com>
> > Reported-by: Eric Wheeler <kvm@lists.ewheeler.net>
> > Closes: https://lore.kernel.org/all/f023d927-52aa-7e08-2ee5-59a2fbc65953@gameservers.com
> > Fixes: a955cad84cda ("KVM: x86/mmu: Retry page fault if root is invalidated by memslot update")
> > Signed-off-by: Sean Christopherson <seanjc@google.com>
>
> What is the git commit id of this change in Linus's tree?
There is none. Commit ba6e3fe25543 (landed in v6.3) unknowingly fixed the bug as
part of a completely unrelated refactoring.
next prev parent reply other threads:[~2023-08-24 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 1:01 [PATCH 6.1] KVM: x86/mmu: Fix an sign-extension bug with mmu_seq that hangs vCPUs Sean Christopherson
2023-08-24 6:53 ` Greg Kroah-Hartman
2023-08-24 13:46 ` Sean Christopherson [this message]
2023-08-24 14:46 ` Greg Kroah-Hartman
2023-08-26 16:46 ` Greg Kroah-Hartman
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=ZOdfU1zQ4UCQNVpz@google.com \
--to=seanjc@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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