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