From: Marc Zyngier <maz@kernel.org>
To: Wei-Lin Chang <weilin.chang@arm.com>
Cc: sashiko-reviews@lists.linux.dev, kvmarm@lists.linux.dev,
Oliver Upton <oupton@kernel.org>
Subject: Re: [PATCH v1 1/3] KVM: arm64: nv: Don't advertise FEAT_LPA2 for guest stage-1
Date: Fri, 11 Sep 2026 09:22:45 +0100 [thread overview]
Message-ID: <86qzj06vu2.wl-maz@kernel.org> (raw)
In-Reply-To: <hucdlhnem5q2ykqxpxu4czjmac5uhazt5jbvgkawh6yqoidnhg@7p74vks5cqx6>
On Thu, 10 Sep 2026 11:56:05 +0100,
Wei-Lin Chang <weilin.chang@arm.com> wrote:
>
> On Wed, Sep 09, 2026 at 10:44:58PM +0000, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [Medium] Equality checks for TGRAN4 and TGRAN16 fail to mask future architectural enum values, leaking unsupported hardware capabilities to NV guests.
> > --
> >
> > commit 6c2ebbb5542b3e22eaee90b7cf8d8cbbc9704e7c
> > Author: Wei-Lin Chang <weilin.chang@arm.com>
> >
> > KVM: arm64: nv: Don't advertise FEAT_LPA2 for guest stage-1
> >
> > There is no FEAT_LPA2 support for NV guests as of now, but we missed
> > limiting it for the non-stage-2 granule size fields (TGRAN4, TGRAN16) in
> > ID_AA64MMFR0_EL1. Add the sanitisation.
> >
> > > diff --git a/arch/arm64/kvm/nested.c b/arch/arm64/kvm/nested.c
> > > index 17123f0b6daba..4d1884b32fc48 100644
> > > --- a/arch/arm64/kvm/nested.c
> > > +++ b/arch/arm64/kvm/nested.c
> > > @@ -1731,6 +1731,19 @@ u64 limit_nv_id_reg(struct kvm *kvm, u32 reg, u64 val)
> > > /* Hide CNTPOFF if present */
> > > val = ID_REG_LIMIT_FIELD_ENUM(val, ID_AA64MMFR0_EL1, ECV, IMP);
> > >
> > > + /* NV does not support FEAT_LPA2. */
> > > + if (SYS_FIELD_GET(ID_AA64MMFR0_EL1, TGRAN4, val) ==
> > > + ID_AA64MMFR0_EL1_TGRAN4_52_BIT) {
> >
> > [Severity: Medium]
> > Will this exact equality check fail to mask future architectural enum values?
> >
> > If future hardware implements a capability enum value greater than 52_BIT for
> > TGRAN4, this check will evaluate to false, leaking the unsupported capability
> > to NV guests.
> >
> > Could this be capped instead, perhaps using inequalities or the
> > ID_REG_LIMIT_FIELD_ENUM macro, to maintain forward compatibility?
>
> ID_REG_LIMIT_FIELD_ENUM works only for unsigned fields, perhaps it is
> worth extending it so it can deal with signed enums too.
Don't bother. We're not doing "crystal ball architecture".
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-09-11 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 22:20 [PATCH v1 0/3] KVM: arm64: Properly advertise !FEAT_LPA2 for NV Wei-Lin Chang
2026-09-09 22:20 ` [PATCH v1 1/3] KVM: arm64: nv: Don't advertise FEAT_LPA2 for guest stage-1 Wei-Lin Chang
2026-09-09 22:44 ` sashiko-bot
2026-09-10 10:56 ` Wei-Lin Chang
2026-09-11 8:22 ` Marc Zyngier [this message]
2026-09-11 9:08 ` Marc Zyngier
2026-09-09 22:20 ` [PATCH v1 2/3] arm64: sysreg: Add TCR_EL2 to sysreg infrastructure Wei-Lin Chang
2026-09-09 22:38 ` sashiko-bot
2026-09-10 10:58 ` Wei-Lin Chang
2026-09-11 8:45 ` Marc Zyngier
2026-09-10 11:54 ` Mark Brown
2026-09-09 22:20 ` [PATCH v1 3/3] KVM: arm64: Convert TCR_EL2 to config-driven sanitisation Wei-Lin Chang
2026-09-11 9:04 ` Marc Zyngier
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=86qzj06vu2.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=weilin.chang@arm.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