From: patchwork-bot+linux-riscv@kernel.org
To: Aamir Ahmed <elb12345@hotmail.co.uk>
Cc: linux-riscv@lists.infradead.org, dfustini@oss.tenstorrent.com,
jms@oss.tenstorrent.com, sboyd@kernel.org,
bmasney+clk@redhat.com, jbrunet+clk@baylibre.com,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
asrinivasan@oss.tenstorrent.com, kees@kernel.org,
linux-hardening@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] clk: tenstorrent: Assign .num before accessing .hws
Date: Sun, 01 Nov 2026 22:17:03 +0000 [thread overview]
Message-ID: <179357142379.2624073.14814247366912220033.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AS8P251MB00013BD9A093C06D2D60E10EC8B42@AS8P251MB0001.EURP251.PROD.OUTLOOK.COM>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Drew Fustini (Tenstorrent) <fustini@kernel.org>:
On Sat, 5 Sep 2026 21:48:35 +0100 you wrote:
> Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with
> __counted_by") annotated the hws member of 'struct clk_hw_onecell_data'
> with __counted_by, which informs the bounds sanitizer (UBSAN_BOUNDS)
> about the number of elements in .hws[], so that it can warn when .hws[]
> is accessed out of bounds. As noted in that change, the __counted_by
> member must be initialized with the number of elements before the first
> array access happens, otherwise there will be a warning from each access
> prior to the initialization because the number of elements is zero.
> This occurs in atlantis_prcm_clocks_register() due to .num being
> assigned only after every clock has been stored in .hws[]. With
> CONFIG_UBSAN_BOUNDS and a compiler that implements __counted_by (GCC
> 15.1+ or Clang 20.1+), this triggers an array-index-out-of-bounds report
> during probe, and with CONFIG_UBSAN_TRAP the first store traps so the
> clock provider never registers.
>
> [...]
Here is the summary with links:
- clk: tenstorrent: Assign .num before accessing .hws
https://git.kernel.org/riscv/c/da9f1312b06e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-01 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 20:48 Aamir Ahmed
2026-09-08 2:56 ` Gustavo A. R. Silva
2026-09-10 0:47 ` Aamir Ahmed
2026-09-24 2:13 ` Drew Fustini
2026-09-29 19:55 ` Drew Fustini
2026-09-09 15:02 ` Anirudh Srinivasan
2026-11-01 22:17 ` patchwork-bot+linux-riscv [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=179357142379.2624073.14814247366912220033.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=bmasney+clk@redhat.com \
--cc=dfustini@oss.tenstorrent.com \
--cc=elb12345@hotmail.co.uk \
--cc=jbrunet+clk@baylibre.com \
--cc=jms@oss.tenstorrent.com \
--cc=kees@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sboyd@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 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®