From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, pbonzini@redhat.com, kvm@vger.kernel.org,
Bjoern Doebel <doebel@amazon.de>
Subject: Re: [PATCH 6.18.y 0/3] Backport nested EPT violation GVA bit fix
Date: Fri, 30 Oct 2026 14:12:23 -0700 [thread overview]
Message-ID: <auUINwzMTjKCrzZA@google.com> (raw)
In-Reply-To: <2026-10-30-1-daily-reply-0005-kvm-nested-ept-gva-6-18@kernel.org>
On Fri, Oct 30, 2026, Sasha Levin wrote:
> > Backport of commit 96b067b59ad9 ("KVM: VMX: Synthesize nested EPT
> > violation GVA_IS_VALID/GVA_TRANSLATED bits") to 6.18.y, with its two
> > dependencies.
>
> KVM x86 opts out of stable by default (Documentation/process/maintainer-kvm-x86.rst),
> and none of the three commits carries Cc: stable or a Fixes: tag.
>
> Bjoern, could you get Sean or Paolo to ack this series (and the matching
> 6.12.y one) on the thread? I will pick both up once they have.
I've seen them and they're on my todo list. I'll try to look at them early next
week.
prev parent reply other threads:[~2026-10-30 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 10:36 [PATCH 6.18.y 0/3] Backport nested EPT violation GVA bit fix Bjoern Doebel
2026-10-30 10:36 ` [PATCH 6.18.y 1/3] KVM: x86/mmu: pass PFERR_GUEST_PAGE/FINAL_MASK to kvm_translate_gpa Bjoern Doebel
2026-10-30 10:36 ` [PATCH 6.18.y 2/3] KVM: x86: Tell ->inject_page_fault() whether or a fault came from hardware Bjoern Doebel
2026-10-30 10:36 ` [PATCH 6.18.y 3/3] KVM: VMX: Synthesize nested EPT violation GVA_IS_VALID/GVA_TRANSLATED bits Bjoern Doebel
2026-10-30 20:54 ` [PATCH 6.18.y 0/3] Backport nested EPT violation GVA bit fix Sasha Levin
2026-10-30 21:12 ` Sean Christopherson [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=auUINwzMTjKCrzZA@google.com \
--to=seanjc@google.com \
--cc=doebel@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.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