From: Zenghui Yu <zenghui.yu@linux.dev>
To: Zhu Ling <zhuling2709@phytium.com.cn>
Cc: maz@kernel.org, tglx@kernel.org, radu@rendec.net,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] irqchip/gic: Fix UBSAN shift-out-of-bounds in GIC helpers
Date: Wed, 23 Sep 2026 17:20:10 +0800 [thread overview]
Message-ID: <5e42a314-41f6-484a-8c3d-c913b5405889@linux.dev> (raw)
In-Reply-To: <20260923082804.13197-1-zhuling2709@phytium.com.cn>
On 9/23/26 4:28 PM, Zhu Ling wrote:
> When running with UBSAN enabled, enabling a GPIO controller that uses a
> GIC interrupt as its parent triggers several shift-out-of-bounds warnings:
>
> shift-out-of-bounds in drivers/irqchip/irq-gic-common.c:50:21
> left shift of 2 by 30 places cannot be represented in type 'int'
>
> Similar reports are emitted from gic_poke_irq() and gic_peek_irq() in
> drivers/irqchip/irq-gic-v3.c. The corresponding GICv2 helpers use the
> same signed-shift pattern. These masks are generated by shifting signed
> integer constants, which invokes undefined behavior when bit 31 is
> selected.
>
> Use BIT() to generate the masks with an unsigned type and make their
> intent explicit.
>
> Signed-off-by: Zhu Ling <zhuling2709@phytium.com.cn>
> ---
> Changes in v3:
> - Fix the same issue in the GICv2 gic_poke_irq() and gic_peek_irq()
> helpers, as pointed out by Zenghui.
>
> Changes in v2:
> - Use BIT() instead of explicit unsigned shifts, as suggested by Marc.
> - Drop the redundant introductory text from the email.
> - Update the author email address.
>
> Link: https://lore.kernel.org/r/2fJDwUUYdEf2_eaRa041L9xkT8RkSWFeo7euOnqMbbPhUatLlEaAvGfB6sOspDmXaxO87Eh7bQLV9UolyjbMtZBT1wB2UGypjPOo0Z-RC0Q=@proton.me
> ---
> drivers/irqchip/irq-gic-common.c | 2 +-
> drivers/irqchip/irq-gic-v3.c | 4 ++--
> drivers/irqchip/irq-gic.c | 4 ++--
> 3 files changed, 5 insertions(+), 5 deletions(-)
Looks good,
Reviewed-by: Zenghui Yu (Huawei) <zenghui.yu@linux.dev>
Thanks,
Zenghui
prev parent reply other threads:[~2026-09-23 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 10:53 [PATCH] " zhuling0805
2025-12-02 11:44 ` Marc Zyngier
2026-09-21 2:21 ` [PATCH v2] " Zhu Ling
2026-09-21 9:31 ` Zenghui Yu
2026-09-23 8:21 ` 朱领
2026-09-23 8:28 ` [PATCH v3] " Zhu Ling
2026-09-23 9:20 ` Zenghui Yu [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=5e42a314-41f6-484a-8c3d-c913b5405889@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--cc=tglx@kernel.org \
--cc=zhuling2709@phytium.com.cn \
/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®