Re: FAILED: patch "[PATCH] KVM: x86/mmu: Drop/zap existing present SPTE even when" failed to apply to 5.10-stable tree

[Greg KH <gregkh@linuxfoundation.org>]

On Wed, Apr 01, 2026 at 02:25:25PM -0700, Sean Christopherson wrote:
> 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).

Yeah, my fault, I still "manually" read that, and my script properly
spit out:

	Commit id aad885e774966e97b675dfe928da164214a71605
		queued in:	queue-6.19/kvm-x86-mmu-drop-zap-existing-present-spte-even-when-creating-an-mmio-spte.patch
		queued in:	queue-6.18/kvm-x86-mmu-drop-zap-existing-present-spte-even-when-creating-an-mmio-spte.patch
		queued in:	queue-6.12/kvm-x86-mmu-drop-zap-existing-present-spte-even-when-creating-an-mmio-spte.patch
		queued in:	queue-6.6/kvm-x86-mmu-drop-zap-existing-present-spte-even-when-creating-an-mmio-spte.patch
		fixed in:	5.13
	> ○ 6.19
	  ○ 6.18
	  ○ 6.12
	  ○ 6.6
	  ○ 6.1
	  ○ 5.15
	  ○ 5.10

But I guess I seleced "5.10" accidentally as well.

Sorry about that, my fault, one of these days I'll make the script a bit
smarter to "pre-populate" the checkboxes with what it thinks should be
happening here, and not require me to actually read values :)

thanks,

greg k-h