[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2024040500-rally-each-3b44@gregkh>
Date: Fri, 5 Apr 2024 11:35:08 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Sean Christopherson <seanjc@...gle.com>
Cc: stable@...r.kernel.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
David Matlack <dmatlack@...gle.com>,
Pasha Tatashin <tatashin@...gle.com>,
Michael Krebs <mkrebs@...gle.com>,
Jim Mattson <jmattson@...gle.com>
Subject: Re: [PATCH 5.15 0/2] KVM: x86: Fix for dirty logging emulated atomics
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
Powered by blists - more mailing lists