From: Zenghui Yu <zenghui.yu@linux.dev>
To: Khushit Shah <khushit.shah@nutanix.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Shameer Kolothum <skolothumtho@nvidia.com>,
Oliver Upton <oupton@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1] arm64: errata: pass REVIDR when matching target implementation CPUs
Date: Wed, 2 Sep 2026 19:46:08 +0800 [thread overview]
Message-ID: <4a941947-04c5-4be8-9d69-3c131775d307@linux.dev> (raw)
In-Reply-To: <20260831105444.4065831-1-khushit.shah@nutanix.com>
On 8/31/26 6:54 PM, Khushit Shah wrote:
> When target implementation CPUs are provided, is_affected_midr_range()
> accidentally passed the MIDR as both arguments to __is_affected_midr_range(),
> so the REVIDR mask check operated on the wrong register.
>
> Pass REVIDR as intended.
>
> Fixes: 86edf6bdcf05 ("smccc/kvm_guest: Enable errata based on implementation CPUs")
> Cc: stable@vger.kernel.org
> Signed-off-by: Khushit Shah <khushit.shah@nutanix.com>
> ---
> arch/arm64/kernel/cpu_errata.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
> index 5db8f0619e4b..b33dccfafaf8 100644
> --- a/arch/arm64/kernel/cpu_errata.c
> +++ b/arch/arm64/kernel/cpu_errata.c
> @@ -82,7 +82,7 @@ is_affected_midr_range(const struct arm64_cpu_capabilities *entry, int scope)
>
> for (i = 0; i < target_impl_cpu_num; i++) {
> if (__is_affected_midr_range(entry, target_impl_cpus[i].midr,
> - target_impl_cpus[i].midr))
> + target_impl_cpus[i].revidr))
> return true;
> }
> return false;
Reviewed-by: Zenghui Yu (Huawei) <zenghui.yu@linux.dev>
Thanks,
Zenghui
next prev parent reply other threads:[~2026-09-02 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 10:54 [PATCH v1] arm64: errata: pass REVIDR when matching target implementation CPUs Khushit Shah
2026-09-01 11:27 ` Shameer Kolothum Thodi
2026-09-02 7:50 ` Marc Zyngier
2026-09-02 11:46 ` Zenghui Yu [this message]
2026-09-03 13:59 ` Will Deacon
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=4a941947-04c5-4be8-9d69-3c131775d307@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=khushit.shah@nutanix.com \
--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=skolothumtho@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=will@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.