From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
media-ci@linuxtv.org, neil.armstrong@linaro.org
Subject: Re: [PATCH 3/3] media: samsung: exynos4-is: Make sure clk_init_data is fully initialized
Date: Fri, 21 Aug 2026 10:15:02 +0000 [thread overview]
Message-ID: <20260821101502.F29471F000E9@smtp.kernel.org> (raw)
In-Reply-To: <2cace1b92cc8333eca63874de17dd5d5b1f9e5d6.1787240035.git.geert+renesas@glider.be>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Double free and use-after-free of device node references in OF iterator loop.
--
--- Patch [3]: [PATCH 3/3] media: samsung: exynos4-is: Make sure clk_init_data is fully initialized ---
commit f3a10ad891243d9b897aed17537077a8bb8725bc
Author: Geert Uytterhoeven <geert+renesas@glider.be>
media: samsung: exynos4-is: Make sure clk_init_data is fully initialized
The clk_init_data structure contains mutually-exclusive members for
specifying clock parents. This commit ensures all members are fully
initialized to zero, preventing subtle bugs with uninitialized data.
> diff --git a/drivers/media/platform/samsung/exynos4-is/media-dev.c b/drivers/media/platform/samsung/exynos4-is/media-dev.c
> index 2e08c4435859e..638babf528221 100644
> --- a/drivers/media/platform/samsung/exynos4-is/media-dev.c
> +++ b/drivers/media/platform/samsung/exynos4-is/media-dev.c
> @@ -1313,7 +1313,7 @@ static int fimc_md_register_clk_provider(struct fimc_md *fmd)
>
> for (i = 0; i < FIMC_MAX_CAMCLKS; i++) {
> struct cam_clk *camclk = &cp->camclk[i];
> - struct clk_init_data init;
> + struct clk_init_data init = {};
> const char *p_name;
>
> ret = of_property_read_string_index(dev->of_node,
[Severity: High]
This is a pre-existing issue, but I noticed a potential double-free of device
node references elsewhere in this file.
Looking at fimc_md_parse_port_node(), it iterates over child nodes using the
scoped iterator macro:
drivers/media/platform/samsung/exynos4-is/media-dev.c:fimc_md_parse_port_node() {
...
for_each_child_of_node_scoped(port, ep) {
ret = fimc_md_parse_one_endpoint(fmd, ep);
if (ret < 0)
return ret;
}
...
}
This macro automatically manages the reference counting for ep, dropping it
implicitly when the loop advances or exits.
However, inside fimc_md_parse_one_endpoint(), the code explicitly calls
of_node_put(ep) on all paths:
drivers/media/platform/samsung/exynos4-is/media-dev.c:fimc_md_parse_one_endpoint() {
...
asd = v4l2_async_nf_add_fwnode_remote(&fmd->subdev_notifier,
of_fwnode_handle(ep),
struct v4l2_async_connection);
of_node_put(ep);
...
}
Because the reference is already dropped in the helper function, wouldn't the
subsequent put by the iterator's loop advance or scope exit result in a
double-free and a use-after-free of the device node?
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1787240035.git.geert+renesas@glider.be?part=3
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
media-ci@linuxtv.org, neil.armstrong@linaro.org
Subject: Re: [PATCH 3/3] media: samsung: exynos4-is: Make sure clk_init_data is fully initialized
Date: Fri, 21 Aug 2026 10:15:02 +0000 [thread overview]
Message-ID: <20260821101502.F29471F000E9@smtp.kernel.org> (raw)
In-Reply-To: <2cace1b92cc8333eca63874de17dd5d5b1f9e5d6.1787240035.git.geert+renesas@glider.be>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Double free and use-after-free of device node references in OF iterator loop.
--
--- Patch [3]: [PATCH 3/3] media: samsung: exynos4-is: Make sure clk_init_data is fully initialized ---
commit f3a10ad891243d9b897aed17537077a8bb8725bc
Author: Geert Uytterhoeven <geert+renesas@glider.be>
media: samsung: exynos4-is: Make sure clk_init_data is fully initialized
The clk_init_data structure contains mutually-exclusive members for
specifying clock parents. This commit ensures all members are fully
initialized to zero, preventing subtle bugs with uninitialized data.
> diff --git a/drivers/media/platform/samsung/exynos4-is/media-dev.c b/drivers/media/platform/samsung/exynos4-is/media-dev.c
> index 2e08c4435859e..638babf528221 100644
> --- a/drivers/media/platform/samsung/exynos4-is/media-dev.c
> +++ b/drivers/media/platform/samsung/exynos4-is/media-dev.c
> @@ -1313,7 +1313,7 @@ static int fimc_md_register_clk_provider(struct fimc_md *fmd)
>
> for (i = 0; i < FIMC_MAX_CAMCLKS; i++) {
> struct cam_clk *camclk = &cp->camclk[i];
> - struct clk_init_data init;
> + struct clk_init_data init = {};
> const char *p_name;
>
> ret = of_property_read_string_index(dev->of_node,
[Severity: High]
This is a pre-existing issue, but I noticed a potential double-free of device
node references elsewhere in this file.
Looking at fimc_md_parse_port_node(), it iterates over child nodes using the
scoped iterator macro:
drivers/media/platform/samsung/exynos4-is/media-dev.c:fimc_md_parse_port_node() {
...
for_each_child_of_node_scoped(port, ep) {
ret = fimc_md_parse_one_endpoint(fmd, ep);
if (ret < 0)
return ret;
}
...
}
This macro automatically manages the reference counting for ep, dropping it
implicitly when the loop advances or exits.
However, inside fimc_md_parse_one_endpoint(), the code explicitly calls
of_node_put(ep) on all paths:
drivers/media/platform/samsung/exynos4-is/media-dev.c:fimc_md_parse_one_endpoint() {
...
asd = v4l2_async_nf_add_fwnode_remote(&fmd->subdev_notifier,
of_fwnode_handle(ep),
struct v4l2_async_connection);
of_node_put(ep);
...
}
Because the reference is already dropped in the helper function, wouldn't the
subsequent put by the iterator's loop advance or scope exit result in a
double-free and a use-after-free of the device node?
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1787240035.git.geert+renesas@glider.be?part=3
next prev parent reply other threads:[~2026-08-21 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 10:04 [PATCH 0/3] media: Make sure clk_init_data is fully initialized Geert Uytterhoeven
2026-08-21 10:04 ` Geert Uytterhoeven
2026-08-21 10:04 ` [PATCH 1/3] media: cec: meson: ao-cec-g12a: " Geert Uytterhoeven
2026-08-21 10:04 ` Geert Uytterhoeven
2026-08-21 10:04 ` [PATCH 2/3] media: microchip: " Geert Uytterhoeven
2026-08-21 10:04 ` Geert Uytterhoeven
2026-08-27 5:59 ` Eugen Hristev
2026-08-27 5:59 ` Eugen Hristev
2026-08-21 10:04 ` [PATCH 3/3] media: samsung: exynos4-is: " Geert Uytterhoeven
2026-08-21 10:04 ` Geert Uytterhoeven
2026-08-21 10:15 ` sashiko-bot [this message]
2026-08-21 10:15 ` sashiko-bot
2026-08-24 15:19 ` [PATCH 0/3] media: " Brian Masney
2026-08-24 15:19 ` Brian Masney
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=20260821101502.F29471F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=neil.armstrong@linaro.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.