All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: "Sukrit.Bhatnagar@sony.com" <Sukrit.Bhatnagar@sony.com>
Cc: "stable@vger.kernel.org" <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: Mon, 24 Nov 2025 07:47:00 -0800	[thread overview]
Message-ID: <aSR99JOY-BjAKapl@google.com> (raw)
In-Reply-To: <TY7PR01MB1503836F91731DC7C6D4A3E12F6D3A@TY7PR01MB15038.jpnprd01.prod.outlook.com>

On Sun, Nov 23, 2025, Sukrit.Bhatnagar@sony.com wrote:
> On 2025-11-22 03:11, Sean Christopherson wrote:
> > 
> > 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).
>  
> 
> This commit did not apply cleanly to the 6.12-stable tree,
> as notified earlier by Greg's mail. 6.17-stable seemed to
> have no issues.
> 
> The function handle_ept_violation got some changes in v6.16
>   c8563d1b6998 ("KVM: VMX: Split out guts of EPT violation to common/exposed function")
> which moved the code from vmx/vmx.c to vmx/common.h.
> So, v6.16+ is ok, but not the earlier ones.
> 
> I think this manual backport commit is needed.
> Please let me know if my understanding is not correct.

Ah, your understanding is correct.  I saw that the commit was queue for 6.12 (and
landed in 6.12 as commit 3010739f53438) and assumed it was a clean backport.  But
I missed Sasha's Stable-dep-of magic intervention[2].

So this backport is _now_ unnecessary, but was necessary when you sent the patch.

Thanks for the backport and follow-up, much appreciated even though Sasha-bot
stole your thunder :-)

[1] https://lore.kernel.org/all/20251121130150.019304053@linuxfoundation.org
[2] https://lore.kernel.org/all/20251120181940.1924069-1-sashal@kernel.org

  reply	other threads:[~2025-11-24 15:47 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
2025-11-23 10:08   ` Sukrit.Bhatnagar
2025-11-24 15:47     ` Sean Christopherson [this message]
  -- 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=aSR99JOY-BjAKapl@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.