From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Kenta Akagi <k@mgml.me>,
dmatlack@google.com, isaku.yamahata@intel.com,
pbonzini@redhat.com
Subject: Re: [PATCH 5.15.y 6/6] KVM: x86/mmu: Rename __direct_map() to direct_map()
Date: Sat, 22 Aug 2026 23:42:44 -0400 [thread overview]
Message-ID: <20260822221000.rc-kvm-5.15-orphans@kernel.org> (raw)
In-Reply-To: <010601a02454bfc0-33fc8bd0-1233-4be1-a122-da1f9490105d-000000@ap-northeast-1.amazonses.com>
On Fri, Aug 21, 2026 at 12:38:49PM +0000, Kenta Akagi wrote:
>Maybe I'm missing something, but commit 2abd5287f083 ("KVM: x86: Check for
>invalid/obsolete root *after* making MMU pages available") cannot be backported
>as-is. It depends on is_page_fault_stale(), introduced by commit a955cad84cda
>("KVM: x86/mmu: Retry page fault if root is invalidated by memslot update"),
>which is missing in 5.15.y.
You're not missing anything - you're right.
I've dropped all six from the 5.15 queue.
>I plan to send a manual backport of a955cad84cda and 2abd5287f083.
Please do, and thanks for offering.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-23 3:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 6:52 FAILED: patch "[PATCH] KVM: x86: Check for invalid/obsolete root *after* making MMU" failed to apply to 5.15-stable tree gregkh
2026-07-30 19:29 ` [PATCH 5.15.y 1/6] KVM: x86/mmu: Directly "destroy" PTE list when recycling rmaps Sasha Levin
2026-07-30 19:29 ` [PATCH 5.15.y 2/6] KVM: x86/mmu: Rename pte_list_{destroy,remove}() to show they zap SPTEs Sasha Levin
2026-07-30 19:29 ` [PATCH 5.15.y 3/6] KVM: x86/mmu: Document the "rules" for using host_pfn_mapping_level() Sasha Levin
2026-07-30 19:29 ` [PATCH 5.15.y 4/6] KVM: Rename mmu_notifier_* to mmu_invalidate_* Sasha Levin
2026-07-30 19:29 ` [PATCH 5.15.y 5/6] KVM: x86/mmu: Split out TDP MMU page fault handling Sasha Levin
2026-07-30 19:29 ` [PATCH 5.15.y 6/6] KVM: x86/mmu: Rename __direct_map() to direct_map() Sasha Levin
2026-08-06 16:19 ` Harshit Mogalapalli
2026-08-06 16:50 ` Sasha Levin
2026-08-21 12:38 ` Kenta Akagi
2026-08-23 3:42 ` Sasha Levin [this message]
2026-08-23 13:07 ` [PATCH 5.15.y v2 0/8] backport for CVE-2026-64561 Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 1/8] KVM: x86/mmu: Retry page fault if root is invalidated by memslot update Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 2/8] KVM: x86/mmu: Directly "destroy" PTE list when recycling rmaps Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 3/8] KVM: x86/mmu: Rename pte_list_{destroy,remove}() to show they zap SPTEs Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 4/8] KVM: x86/mmu: Document the "rules" for using host_pfn_mapping_level() Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 5/8] KVM: Rename mmu_notifier_* to mmu_invalidate_* Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 6/8] KVM: x86/mmu: Split out TDP MMU page fault handling Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 7/8] KVM: x86/mmu: Rename __direct_map() to direct_map() Kenta Akagi
2026-08-23 13:07 ` [PATCH 5.15.y v2 8/8] KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Kenta Akagi
2026-08-25 11:49 ` [PATCH 5.15.y v2 0/8] backport for CVE-2026-64561 Sasha Levin
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=20260822221000.rc-kvm-5.15-orphans@kernel.org \
--to=sashal@kernel.org \
--cc=dmatlack@google.com \
--cc=isaku.yamahata@intel.com \
--cc=k@mgml.me \
--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 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.