From: Sean Christopherson <seanjc@google.com>
To: gregkh@linuxfoundation.org
Cc: bkov@amazon.com, fgriffo@amazon.co.uk, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: x86/mmu: Drop/zap existing present SPTE even when" failed to apply to 5.10-stable tree
Date: Wed, 1 Apr 2026 14:25:25 -0700 [thread overview]
Message-ID: <ac2NRUTLk-yX13va@google.com> (raw)
In-Reply-To: <2026033039-occupy-slush-db02@gregkh>
On Mon, Mar 30, 2026, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 5.10-stable tree.
...
> Fixes: a54aa15c6bda3 ("KVM: x86/mmu: Handle MMIO SPTEs directly in mmu_set_spte()")
> Cc: stable@vger.kernel.org
Partially out of curiosity, partially to reduce the probability of future goofs,
why did the tooling try to apply a patch to a kernel without the Fixes commit?
5.10 doesn't have a54aa15c6bda3 and so doesn't need this fix.
I assumed that having an explicit Fixes would implicit scope the backport to
kernels with that commit (or a backport of that commit).
next prev parent reply other threads:[~2026-04-01 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 9:39 FAILED: patch "[PATCH] KVM: x86/mmu: Drop/zap existing present SPTE even when" failed to apply to 5.10-stable tree gregkh
2026-04-01 0:44 ` [PATCH 5.10.y] KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE Sasha Levin
2026-04-01 21:22 ` Sean Christopherson
2026-04-01 21:25 ` Sean Christopherson [this message]
2026-04-02 3:49 ` FAILED: patch "[PATCH] KVM: x86/mmu: Drop/zap existing present SPTE even when" failed to apply to 5.10-stable tree 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=ac2NRUTLk-yX13va@google.com \
--to=seanjc@google.com \
--cc=bkov@amazon.com \
--cc=fgriffo@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--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