From: Nathan Gao <zcgao@amazon.com>
To: <pbonzini@redhat.com>
Cc: <bkov@amazon.com>, <doebel@amazon.de>, <fgriffo@amazon.co.uk>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<seanjc@google.com>, <stable@vger.kernel.org>, <zcgao@amazon.com>
Subject: Re: stable backports for "KVM: x86: Fix shadow paging use-after-free due to unexpected GFN"
Date: Thu, 25 Jun 2026 15:04:37 -0700 [thread overview]
Message-ID: <20260625220437.52368-1-zcgao@amazon.com> (raw)
In-Reply-To: <CABgObfawkiKRDz0to=oCjo1vygVAkHyZXAzpsLWT2GXwkszV_A@mail.gmail.com>
Thanks Paolo! I tested these in the context of Amazon Linux, carrying the
series as a downstream patch set on top of our 5.10 and 5.15 trees, as
follows.
Test setup
- Trees: Amazon Linux 5.10 and 5.15, with the backports applied as
downstream patches. (For 5.10, applied a83e50d86^..d3d0e6688; for 5.15,
applied 4db658c99^..1ab8cd246)
- For each tree we ran with EPT enabled and disabled, i.e.
sudo rmmod kvm_intel && sudo modprobe kvm_intel ept=0
and confirmed via /sys/module/kvm_intel/parameters/ept.
- Tested with AWS EC2 c5.metal.
Tests
- KVM selftests: make -C tools/testing/selftests/kvm run_tests
- kvm-unit-tests: https://www.linux-kvm.org/page/KVM-unit-tests
For each (tree x EPT setting) we collected results before and after
applying the backport and compared them.
Results
- No regressions. On both 5.10 and 5.15, and with EPT on and off, the
test outcomes are the same before and after the backport.
- kvm-unit-tests output was identical before vs. after.
- The KVM selftest verdicts (ok/not ok) were identical before vs. after.
The handful of failing tests are pre-existing on our baseline and
unrelated to the MMU change (e.g. debug_regs, vmx_pmu_msrs_test, a
memslot_perf_test timeout, etc.).
So from these tests, the backport looks good. Please let me know if
there are any other tests I can help with.
Tested-by: Nathan Gao <zcgao@amazon.com>
Thanks,
Nathan Gao
next prev parent reply other threads:[~2026-06-25 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 20:10 [PATCH] KVM: x86: Fix shadow paging use-after-free due to unexpected GFN Paolo Bonzini
2026-05-05 10:13 ` stable backports for "KVM: x86: Fix shadow paging use-after-free due to unexpected GFN" Paolo Bonzini
2026-05-29 8:37 ` Bjoern Doebel
2026-06-20 5:40 ` Paolo Bonzini
2026-06-25 22:04 ` Nathan Gao [this message]
2026-06-30 2:33 ` Nathan Gao
2026-06-30 22:37 ` Nathan Gao
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=20260625220437.52368-1-zcgao@amazon.com \
--to=zcgao@amazon.com \
--cc=bkov@amazon.com \
--cc=doebel@amazon.de \
--cc=fgriffo@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®