All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sean Christopherson <seanjc@google.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	David Matlack <dmatlack@google.com>,
	Pasha Tatashin <tatashin@google.com>,
	Michael Krebs <mkrebs@google.com>,
	Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH 5.15 0/2] KVM: x86: Fix for dirty logging emulated atomics
Date: Fri, 5 Apr 2024 11:35:08 +0200	[thread overview]
Message-ID: <2024040500-rally-each-3b44@gregkh> (raw)
In-Reply-To: <20240404234004.911293-1-seanjc@google.com>

On Thu, Apr 04, 2024 at 04:40:02PM -0700, Sean Christopherson wrote:
> Two KVM x86 backports for 5.15.  Patch 2 is the primary motivation (fix
> for potential guest data corruption after live migration).
> 
> Patch 1 is a (very) soft dependency to resolve a conflict.  It's not strictly
> necessary (manually resolving the conflict wouldn't be difficult), but it
> is a fix that has been in upstream for a long time.  The only reason I didn't
> tag it for stable from the get-go is that the bug it fixes is very
> theoretical.  At this point, the odds of the patch causing problems are
> lower than the odds of me botching a manual backport.
> 
> Sean Christopherson (2):
>   KVM: x86: Bail to userspace if emulation of atomic user access faults
>   KVM: x86: Mark target gfn of emulated atomic instruction as dirty
> 
>  arch/x86/kvm/x86.c | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> 
> base-commit: 9465fef4ae351749f7068da8c78af4ca27e61928
> -- 
> 2.44.0.478.gd926399ef9-goog

All now queued up, thanks.

greg k-h

      parent reply	other threads:[~2024-04-05  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 23:40 [PATCH 5.15 0/2] KVM: x86: Fix for dirty logging emulated atomics Sean Christopherson
2024-04-04 23:40 ` [PATCH 5.15 1/2] KVM: x86: Bail to userspace if emulation of atomic user access faults Sean Christopherson
2024-04-04 23:40 ` [PATCH 5.15 2/2] KVM: x86: Mark target gfn of emulated atomic instruction as dirty Sean Christopherson
2024-04-05  9:35 ` Greg Kroah-Hartman [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=2024040500-rally-each-3b44@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dmatlack@google.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrebs@google.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=stable@vger.kernel.org \
    --cc=tatashin@google.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.