From: <nobuhiro.iwamatsu.x90@mail.toshiba>
To: <geert+renesas@glider.be>, <kristo@kernel.org>,
<sboyd@kernel.org>, <bmasney+clk@redhat.com>,
<jbrunet+clk@baylibre.com>, <nuno.sa@analog.com>,
<linux@roeck-us.net>, <Michael.Hennerich@analog.com>,
<antoniu.miclaus@analog.com>, <jic23@kernel.org>,
<dlechner@baylibre.com>, <andy@kernel.org>,
<sunny.luo@amlogic.com>, <xianwei.zhao@amlogic.com>,
<broonie@kernel.org>, <kees@kernel.org>, <khilman@baylibre.com>,
<mathieu.dubois-briand@bootlin.com>
Cc: <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-hwmon@vger.kernel.org>, <linux@analog.com>,
<linux-iio@vger.kernel.org>, <linux-amlogic@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH treewide 2/5] clk: visconti: Make sure clk_init_data is fully initialized
Date: Thu, 20 Aug 2026 02:03:15 +0000 [thread overview]
Message-ID: <TY7PR01MB1481812D226130989DCE5FC1BCDA42@TY7PR01MB14818.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <42dd7be99acbbea1343e2fcc0ba4ffb91f8517ca.1787165329.git.geert+renesas@glider.be>
> -----Original Message-----
> From: Geert Uytterhoeven <geert+renesas@glider.be>
> Sent: Thursday, August 20, 2026 4:05 AM
> To: Tero Kristo <kristo@kernel.org>; Stephen Boyd <sboyd@kernel.org>; Brian
> Masney <bmasney+clk@redhat.com>; Jerome Brunet
> <jbrunet+clk@baylibre.com>; iwamatsu nobuhiro(岩松 信洋 □DITC○C
> PT) <nobuhiro.iwamatsu.x90@mail.toshiba>; Nuno Sa
> <nuno.sa@analog.com>; Guenter Roeck <linux@roeck-us.net>; Michael
> Hennerich <Michael.Hennerich@analog.com>; Antoniu Miclaus
> <antoniu.miclaus@analog.com>; Jonathan Cameron <jic23@kernel.org>;
> David Lechner <dlechner@baylibre.com>; Andy Shevchenko
> <andy@kernel.org>; Sunny Luo <sunny.luo@amlogic.com>; Xianwei Zhao
> <xianwei.zhao@amlogic.com>; Mark Brown <broonie@kernel.org>; Kees
> Cook <kees@kernel.org>; Kevin Hilman <khilman@baylibre.com>; Mathieu
> Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> Cc: linux-omap@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> linux-hwmon@vger.kernel.org; linux@analog.com; linux-iio@vger.kernel.org;
> linux-amlogic@lists.infradead.org; linux-spi@vger.kernel.org;
> linux-clk@vger.kernel.org; linux-kernel@vger.kernel.org; Geert Uytterhoeven
> <geert+renesas@glider.be>
> Subject: [PATCH treewide 2/5] clk: visconti: Make sure clk_init_data is fully
> initialized
>
> The clk_init_data structure contains several mutually-exclusive members for
> different methods to specify the possible parents of a clock, prompting drivers
> to initialize only the members they need. However, not initializing all members
> may cause subtle issues, which are only exposed when
> CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is
> enabled.
>
> visconti_clk_register_gate() fills in init.parent_data, and assumes that
> init.parent_names is NULL. However, the latter in uninitialized, and thus may
> cause a crash.
>
> Make sure all members are fully initialized, to fix such bugs, and to avoid future
> breakage when converting drivers to a different method for specifying the
> parents.
>
> Fixes: b4cbe606dc3674b2 ("clk: visconti: Add support common clock driver
> and reset driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>
Best regards,
Nobuhiro
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-08-20 2:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 19:05 [PATCH treewide 0/5] clk: Make sure clk_init_data is fully initialized (part 1) Geert Uytterhoeven
2026-08-19 19:05 ` [PATCH treewide 1/5] clk: ti: Make sure clk_init_data is fully initialized Geert Uytterhoeven
2026-08-19 19:10 ` sashiko-bot
2026-08-19 21:21 ` Brian Masney
2026-08-20 5:02 ` Mathieu Dubois-Briand
2026-08-20 5:56 ` Stephen Boyd
2026-08-19 19:05 ` [PATCH treewide 2/5] clk: visconti: " Geert Uytterhoeven
2026-08-19 19:14 ` sashiko-bot
2026-08-19 21:21 ` Brian Masney
2026-08-20 2:03 ` nobuhiro.iwamatsu.x90 [this message]
2026-08-20 5:56 ` Stephen Boyd
2026-08-19 19:05 ` [PATCH treewide 3/5] hwmon: (ltc4282) " Geert Uytterhoeven
2026-08-19 19:12 ` sashiko-bot
2026-08-19 20:32 ` Guenter Roeck
2026-08-19 21:22 ` Brian Masney
2026-08-19 19:05 ` [PATCH treewide 4/5] iio: frequency: adf4377: " Geert Uytterhoeven
2026-08-19 19:13 ` sashiko-bot
2026-08-20 7:40 ` Geert Uytterhoeven
2026-08-19 21:22 ` Brian Masney
2026-08-20 1:38 ` Jonathan Cameron
2026-08-19 19:05 ` [PATCH treewide 5/5] spi: amlogic-spisg: " Geert Uytterhoeven
2026-08-19 19:13 ` sashiko-bot
2026-08-19 21:23 ` Brian Masney
2026-08-20 8:49 ` Xianwei Zhao
2026-08-20 12:11 ` (subset) [PATCH treewide 0/5] clk: Make sure clk_init_data is fully initialized (part 1) Mark Brown
2026-08-21 10:16 ` Geert Uytterhoeven
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=TY7PR01MB1481812D226130989DCE5FC1BCDA42@TY7PR01MB14818.jpnprd01.prod.outlook.com \
--to=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=bmasney+clk@redhat.com \
--cc=broonie@kernel.org \
--cc=dlechner@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=jbrunet+clk@baylibre.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@analog.com \
--cc=linux@roeck-us.net \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=nuno.sa@analog.com \
--cc=sboyd@kernel.org \
--cc=sunny.luo@amlogic.com \
--cc=xianwei.zhao@amlogic.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
all inboxes | Powered by JetHome®