From: Biren Pandya <birenpandya@gmail.com>
To: linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
niklas.soderlund@ragnatech.se, mchehab@kernel.org,
geert+renesas@glider.be, magnus.damm@gmail.com,
laurent.pinchart@ideasonboard.com, jacopo.mondi@ideasonboard.com,
Biren Pandya <birenpandya@gmail.com>
Subject: [PATCH v3 3/4] media: renesas: rcar-core: Add missing media_entity_cleanup()
Date: Sat, 4 Jul 2026 23:16:42 +0530 [thread overview]
Message-ID: <20260704174638.66302-9-birenpandya@gmail.com> (raw)
In-Reply-To: <20260704174638.66302-6-birenpandya@gmail.com>
The probe error path and the remove function fail to call
media_entity_cleanup() upon teardown.
While currently a no-op in most cases, calling media_entity_cleanup()
is an API requirement for entities initialized with media_entity_pads_init()
to prevent memory leaks.
Add the missing media_entity_cleanup() calls. Furthermore, introduce a
dedicated err_entity label in the probe error path to ensure the cleanup
is only invoked if media_entity_pads_init() has successfully completed.
Signed-off-by: Biren Pandya <birenpandya@gmail.com>
---
drivers/media/platform/renesas/rcar-vin/rcar-core.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/renesas/rcar-vin/rcar-core.c b/drivers/media/platform/renesas/rcar-vin/rcar-core.c
index c8d564aa1eba..5bae8eb0ee19 100644
--- a/drivers/media/platform/renesas/rcar-vin/rcar-core.c
+++ b/drivers/media/platform/renesas/rcar-vin/rcar-core.c
@@ -1211,7 +1211,7 @@ static int rcar_vin_probe(struct platform_device *pdev)
ret = rvin_create_controls(vin);
if (ret < 0)
- goto err_id;
+ goto err_entity;
switch (vin->info->model) {
case RCAR_GEN3:
@@ -1246,6 +1246,8 @@ static int rcar_vin_probe(struct platform_device *pdev)
err_ctrl:
rvin_free_controls(vin);
+err_entity:
+ media_entity_cleanup(&vin->vdev.entity);
err_id:
rvin_id_put(vin);
err_dma:
@@ -1270,6 +1272,7 @@ static void rcar_vin_remove(struct platform_device *pdev)
rvin_group_put(vin);
rvin_free_controls(vin);
+ media_entity_cleanup(&vin->vdev.entity);
rvin_id_put(vin);
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-07-04 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 17:46 [PATCH v3 0/4] media: renesas: Fix missing media_entity_cleanup() Biren Pandya
2026-07-04 17:46 ` [PATCH v3 1/4] media: renesas: rcar-csi2: Add " Biren Pandya
2026-07-08 15:58 ` Jacopo Mondi
2026-07-04 17:46 ` [PATCH v3 2/4] media: renesas: csisp: " Biren Pandya
2026-07-08 15:54 ` Jacopo Mondi
2026-07-04 17:46 ` Biren Pandya [this message]
2026-07-08 16:01 ` [PATCH v3 3/4] media: renesas: rcar-core: " Jacopo Mondi
2026-07-04 17:46 ` [PATCH v3 4/4] media: renesas: rzg2l-core: " Biren Pandya
2026-07-08 16:02 ` Jacopo Mondi
-- strict thread matches above, loose matches on Subject: below --
2026-06-22 17:33 [PATCH v3 0/4] media: renesas: Fix " Biren Pandya
2026-06-22 17:33 ` [PATCH v3 3/4] media: renesas: rcar-core: Add " Biren Pandya
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=20260704174638.66302-9-birenpandya@gmail.com \
--to=birenpandya@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
/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