From: Vincent Donnefort <vdonnefort@google.com>
To: Wei-Lin Chang <weilin.chang@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sebastian Ene <sebastianene@google.com>,
Itaru Kitayama <itaru.kitayama@fujitsu.com>,
Sashiko AI <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] KVM: arm64: ptdump: Check the page tables aren't freed when accessing
Date: Thu, 17 Sep 2026 09:11:50 +0100 [thread overview]
Message-ID: <aqugxlnqegPzMpB-@google.com> (raw)
In-Reply-To: <20260916230337.4162485-2-weilin.chang@arm.com>
On Thu, Sep 17, 2026 at 12:03:36AM +0100, Wei-Lin Chang wrote:
> An open debugfs file keeps the KVM structure alive, but does not prevent
> mmu notifier release from freeing the stage-2 page tables when the VMM’s
> address space is torn down. Therefore page tables belonging to the mmus
> could have been freed when a thread opens or reads the ptdump files.
> Take the mmu_lock and check mmu->pgt is still alive before accessing the
> page tables.
As Sashiko said, the read_lock is probably enough, including the existing one in
kvm_ptdump_guest_show()
With that change:
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
Tested-by: Vincent Donnefort <vdonnefort@google.com>
>
> Also for the ipa_range file and stage2_levels file, switch from keeping
> the pointer to the page tables to keeping the pointer to the mmu.
>
> Fixes: 7c4f73548ed1 ("KVM: arm64: Register ptdump with debugfs on guest creation")
> Reported-by: Sashiko AI <sashiko-bot@kernel.org>
> Closes: https://lore.kernel.org/kvmarm/20260623144054.B91D21F000E9@smtp.kernel.org/
> Signed-off-by: Wei-Lin Chang <weilin.chang@arm.com>
> Cc: stable@vger.kernel.org
> ---
> arch/arm64/kvm/ptdump.c | 43 +++++++++++++++++++++++++++++++----------
> 1 file changed, 33 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm64/kvm/ptdump.c b/arch/arm64/kvm/ptdump.c
> index 69899797dbad..4ead856c181a 100644
> --- a/arch/arm64/kvm/ptdump.c
> +++ b/arch/arm64/kvm/ptdump.c
> @@ -115,15 +115,28 @@ static int kvm_ptdump_build_levels(struct ptdump_pg_level *level, u32 start_lvl)
>
> static struct kvm_ptdump_guest_state *kvm_ptdump_parser_create(struct kvm_s2_mmu *mmu)
> {
> + struct kvm *kvm = kvm_s2_mmu_to_kvm(mmu);
> struct kvm_ptdump_guest_state *st;
> - struct kvm_pgtable *pgtable = mmu->pgt;
> + s8 start_level;
> int ret;
>
> + /*
> + * We only need the pgt start level to initialize the ptdump, get it
> + * while holding the mmu_lock. It's fine if the pgt gets freed
> + * afterwards, we'll check again when doing the actual dump.
> + */
> + scoped_guard(write_lock, &kvm->mmu_lock) {
> + if (mmu->pgt)
> + start_level = mmu->pgt->start_level;
> + else
> + return ERR_PTR(-ENOENT);
> + }
> +
> st = kzalloc_obj(struct kvm_ptdump_guest_state, GFP_KERNEL_ACCOUNT);
> if (!st)
> return ERR_PTR(-ENOMEM);
>
> - ret = kvm_ptdump_build_levels(&st->level[0], pgtable->start_level);
> + ret = kvm_ptdump_build_levels(&st->level[0], start_level);
> if (ret) {
> kfree(st);
> return ERR_PTR(ret);
> @@ -149,6 +162,9 @@ static int kvm_ptdump_guest_show(struct seq_file *m, void *unused)
> };
>
> guard(write_lock)(&kvm->mmu_lock);
> + if (!mmu->pgt)
> + return 0;
> +
> st->parser_state = (struct ptdump_pg_state) {
> .marker = &st->ipa_marker[0],
> .end_address = BIT(mmu->pgt->ia_bits),
> @@ -211,17 +227,27 @@ static const struct file_operations kvm_ptdump_guest_fops = {
>
> static int kvm_pgtable_range_show(struct seq_file *m, void *unused)
> {
> - struct kvm_pgtable *pgtable = m->private;
> + struct kvm_s2_mmu *mmu = m->private;
> + struct kvm *kvm = kvm_s2_mmu_to_kvm(mmu);
> +
> + guard(write_lock)(&kvm->mmu_lock);
> +
> + if (mmu->pgt)
> + seq_printf(m, "%2u\n", mmu->pgt->ia_bits);
>
> - seq_printf(m, "%2u\n", pgtable->ia_bits);
> return 0;
> }
>
> static int kvm_pgtable_levels_show(struct seq_file *m, void *unused)
> {
> - struct kvm_pgtable *pgtable = m->private;
> + struct kvm_s2_mmu *mmu = m->private;
> + struct kvm *kvm = kvm_s2_mmu_to_kvm(mmu);
> +
> + guard(write_lock)(&kvm->mmu_lock);
> +
> + if (mmu->pgt)
> + seq_printf(m, "%1d\n", KVM_PGTABLE_MAX_LEVELS - mmu->pgt->start_level);
>
> - seq_printf(m, "%1d\n", KVM_PGTABLE_MAX_LEVELS - pgtable->start_level);
> return 0;
> }
>
> @@ -230,15 +256,12 @@ static int kvm_pgtable_debugfs_open(struct inode *m, struct file *file,
> {
> struct kvm_s2_mmu *mmu = m->i_private;
> struct kvm *kvm = kvm_s2_mmu_to_kvm(mmu);
> - struct kvm_pgtable *pgtable;
> int ret;
>
> if (!kvm_get_kvm_safe(kvm))
> return -ENOENT;
>
> - pgtable = mmu->pgt;
> -
> - ret = single_open(file, show, pgtable);
> + ret = single_open(file, show, mmu);
> if (ret < 0)
> kvm_put_kvm(kvm);
> return ret;
> --
> 2.43.0
>
--
Vincent
next prev parent reply other threads:[~2026-09-17 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 23:03 [PATCH v3 0/2] KVM: arm64: ptdump: Shadow ptdump fixes Wei-Lin Chang
2026-09-16 23:03 ` [PATCH v3 1/2] KVM: arm64: ptdump: Check the page tables aren't freed when accessing Wei-Lin Chang
2026-09-17 8:11 ` Vincent Donnefort [this message]
2026-09-17 19:30 ` Wei-Lin Chang
2026-09-16 23:03 ` [PATCH v3 2/2] KVM: arm64: ptdump: Fix shadow ptdump sleep-in-atomic-context problem Wei-Lin Chang
2026-09-17 7:46 ` [PATCH v3 0/2] KVM: arm64: ptdump: Shadow ptdump fixes Itaru Kitayama
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=aqugxlnqegPzMpB-@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=itaru.kitayama@fujitsu.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sebastianene@google.com \
--cc=seiden@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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 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®