From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: rs9: Add clock index range check to rs9_of_clk_get()
Date: Wed, 21 Jan 2026 00:43:37 +0100 [thread overview]
Message-ID: <10de432d-b38a-4fe2-959b-d9fa4e08e6c1@mailbox.org> (raw)
In-Reply-To: <4cb63bd8b1e49407831431fbc88b218f720a74fd.1768899891.git.geert+renesas@glider.be>
On 1/20/26 10:05 AM, Geert Uytterhoeven wrote:
> rs9_of_clk_get() does not validate the clock index in the passed
> DT clock specifier. If DT specifies an incorrect and out-of-range
> index, this will access memory beyond the end of the clk_dif[] array.
>
> Fix by this adding a range check to rs9_of_clk_get().
>
> Fixes: 892e0ddea1aa6f70 ("clk: rs9: Add Renesas 9-series PCIe clock generator driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> This is v2 of "[PATCH] clk: rs9: Convert to clk_hw_onecell_data and
> of_clk_hw_onecell_get()"
> (https://lore.kernel.org/a6dce17b15d29a257d09fe0edc199a14c297f1a8.1768836042.git.geert+renesas@glider.be)
>
> v2:
> - Just add the missing range check; the conversion to
> of_clk_hw_onecell_get() can be done later.
> ---
> drivers/clk/clk-renesas-pcie.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/clk/clk-renesas-pcie.c b/drivers/clk/clk-renesas-pcie.c
> index aa108df12e44fb9f..1adc5365ba1a3d59 100644
> --- a/drivers/clk/clk-renesas-pcie.c
> +++ b/drivers/clk/clk-renesas-pcie.c
> @@ -277,6 +277,9 @@ rs9_of_clk_get(struct of_phandle_args *clkspec, void *data)
> struct rs9_driver_data *rs9 = data;
> unsigned int idx = clkspec->args[0];
>
> + if (idx >= rs9->chip_info->num_clks)
of_clk_src_onecell_get() does a pr_err("%s: invalid clock index %u\n",
__func__, idx); on error, should this function do the same ?
> + return ERR_PTR(-EINVAL);
> +
Thanks !
next prev parent reply other threads:[~2026-01-21 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:05 Geert Uytterhoeven
2026-01-20 23:43 ` Marek Vasut [this message]
2026-01-21 9:34 ` Geert Uytterhoeven
2026-01-21 10:06 ` Marek Vasut
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=10de432d-b38a-4fe2-959b-d9fa4e08e6c1@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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®