From: Hyunwoo Kim <imv4bel@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
oupton@kernel.org, imv4bel@gmail.com
Subject: Re: [PATCH 6.12.y] KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation
Date: Tue, 9 Jun 2026 20:31:41 +0900 [thread overview]
Message-ID: <aif5nV0qvDy6-a9u@v4bel> (raw)
In-Reply-To: <86fr2wt34q.wl-maz@kernel.org>
On Tue, Jun 09, 2026 at 11:33:09AM +0100, Marc Zyngier wrote:
> On Tue, 09 Jun 2026 11:13:36 +0100,
> Hyunwoo Kim <imv4bel@gmail.com> wrote:
> >
> > [ Upstream commit f2ca45b50d4216c9cc7ffabf50d9ad1932209251 ]
> >
> > walk_s1() and kvm_walk_nested_s2() expect to be called while holding
> > kvm->srcu to guard against memslot changes. While this is generally
> > the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the
> > respective walkers without taking kvm->srcu.
> >
> > Fix by acquiring kvm->srcu prior to the table walk in both instances.
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 50f77dc87f13 ("KVM: arm64: Populate level on S1PTW SEA injection")
> > Fixes: be04cebf3e78 ("KVM: arm64: nv: Add emulation of AT S12E{0,1}{R,W}")
> > Suggested-by: Oliver Upton <oupton@kernel.org>
> > Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
> > Reviewed-by: Oliver Upton <oupton@kernel.org>
> > Link: https://patch.msgid.link/aiAZfdeyanIvP8SD@v4bel
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > [ Hyunwoo Kim: __kvm_at_s12() returns void in 6.12.y, so the context
> > differs from upstream (return; instead of return ret;). The
> > __kvm_find_s1_desc_level() hunk (Fixes: 50f77dc87f13) is dropped, as
> > that function is v6.18+ and absent here; only the __kvm_at_s12() /
> > kvm_walk_nested_s2() change (Fixes: be04cebf3e78) applies. ]
> > Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
>
> I don't think this is necessary. 6.12 doesn't actually have NV support
> (it was enabled only from userspace in 6.17), therefore the ATS12
> emulation isn't reachable.
Ah, I see. Thank you for the review.
>
> Thanks,
>
> M.
>
> --
> Without deviation from the norm, progress is not possible.
Best regards,
Hyunwoo Kim
prev parent reply other threads:[~2026-06-09 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:13 [PATCH 6.12.y] KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation Hyunwoo Kim
2026-06-09 10:33 ` Marc Zyngier
2026-06-09 11:31 ` Hyunwoo Kim [this message]
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=aif5nV0qvDy6-a9u@v4bel \
--to=imv4bel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--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 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.