From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Johan Hovold <johan@kernel.org>
Cc: Alain Volmat <alain.volmat@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@collabora.com>
Subject: Re: [PATCH] drm: sti: fix device leaks at component probe
Date: Fri, 31 Oct 2025 18:10:46 +0100 [thread overview]
Message-ID: <aQTtlvoe96Odq96A@thinkstation> (raw)
In-Reply-To: <20250922122012.27407-1-johan@kernel.org>
Hi Johan,
For some reason this thread went through my filters, sorry.
Le Mon, Sep 22, 2025 at 02:20:12PM +0200, Johan Hovold a écrit :
> Make sure to drop the references taken to the vtg devices by
> of_find_device_by_node() when looking up their driver data during
> component probe.
Markus suggested “Prevent device leak in of_vtg_find()” as commit
summary.
>
> Note that holding a reference to a platform device does not prevent its
> driver data from going away so there is no point in keeping the
> reference after the lookup helper returns.
>
> Fixes: cc6b741c6f63 ("drm: sti: remove useless fields from vtg structure")
> Cc: stable@vger.kernel.org # 4.16
> Cc: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
> drivers/gpu/drm/sti/sti_vtg.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/sti/sti_vtg.c b/drivers/gpu/drm/sti/sti_vtg.c
> index ee81691b3203..ce6bc7e7b135 100644
> --- a/drivers/gpu/drm/sti/sti_vtg.c
> +++ b/drivers/gpu/drm/sti/sti_vtg.c
> @@ -143,12 +143,17 @@ struct sti_vtg {
> struct sti_vtg *of_vtg_find(struct device_node *np)
> {
> struct platform_device *pdev;
> + struct sti_vtg *vtg;
>
> pdev = of_find_device_by_node(np);
> if (!pdev)
> return NULL;
>
> - return (struct sti_vtg *)platform_get_drvdata(pdev);
> + vtg = platform_get_drvdata(pdev);
> +
> + put_device(&pdev->dev);
I would prefer of_node_put() instead, which does the same basically, but
at least it is more obviously linked to of_find_device_by_node().
Best regards,
Raphaël
> +
> + return vtg;
> }
>
> static void vtg_reset(struct sti_vtg *vtg)
> --
> 2.49.1
>
next prev parent reply other threads:[~2025-10-31 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 12:20 [PATCH] drm: sti: fix device leaks at component probe Johan Hovold
2025-09-22 16:16 ` Markus Elfring
2025-11-03 18:56 ` Raphaël Gallais-Pou
2025-11-04 8:00 ` Markus Elfring
2025-11-04 11:25 ` Johan Hovold
2025-10-27 13:35 ` Johan Hovold
2025-10-31 17:10 ` Raphaël Gallais-Pou [this message]
2025-11-04 11:21 ` Johan Hovold
2025-11-20 13:13 ` Johan Hovold
2025-11-24 13:27 ` Raphael Gallais-Pou
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=aQTtlvoe96Odq96A@thinkstation \
--to=rgallaispou@gmail.com \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=benjamin.gaignard@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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