From: Sean Christopherson <seanjc@google.com>
To: Sukrit Bhatnagar <Sukrit.Bhatnagar@sony.com>
Cc: stable@vger.kernel.org, Xiaoyao Li <xiaoyao.li@intel.com>
Subject: Re: [PATCH 6.12.y] KVM: VMX: Fix check for valid GVA on an EPT violation
Date: Fri, 21 Nov 2025 10:11:18 -0800 [thread overview]
Message-ID: <aSCrRoe3fcBgLo8W@google.com> (raw)
In-Reply-To: <20251121055209.66918-1-Sukrit.Bhatnagar@sony.com>
On Fri, Nov 21, 2025, Sukrit Bhatnagar wrote:
> On an EPT violation, bit 7 of the exit qualification is set if the
> guest linear-address is valid. The derived page fault error code
> should not be checked for this bit.
>
> Fixes: f3009482512e ("KVM: VMX: Set PFERR_GUEST_{FINAL,PAGE}_MASK if and only if the GVA is valid")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sukrit Bhatnagar <Sukrit.Bhatnagar@sony.com>
> Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> Link: https://patch.msgid.link/20251106052853.3071088-1-Sukrit.Bhatnagar@sony.com
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> (cherry picked from commit d0164c161923ac303bd843e04ebe95cfd03c6e19)
> Signed-off-by: Sukrit Bhatnagar <Sukrit.Bhatnagar@sony.com>
> ---
No need for the manual "backport", commits that are tagged for stable@ are
automically pulled into LTS kernels so long as they apply cleanly (and obviously
don't cause problems).
next prev parent reply other threads:[~2025-11-21 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 5:52 [PATCH 6.12.y] KVM: VMX: Fix check for valid GVA on an EPT violation Sukrit Bhatnagar
2025-11-21 18:11 ` Sean Christopherson [this message]
2025-11-23 10:08 ` Sukrit.Bhatnagar
2025-11-24 15:47 ` Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 15:51 FAILED: patch "[PATCH] KVM: VMX: Fix check for valid GVA on an EPT violation" failed to apply to 6.12-stable tree gregkh
2025-11-21 5:53 ` [PATCH 6.12.y] KVM: VMX: Fix check for valid GVA on an EPT violation Sukrit Bhatnagar
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=aSCrRoe3fcBgLo8W@google.com \
--to=seanjc@google.com \
--cc=Sukrit.Bhatnagar@sony.com \
--cc=stable@vger.kernel.org \
--cc=xiaoyao.li@intel.com \
/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.