From: Aleksandr Chubuchnyi <chubuchnyi@gmail.com>
To: sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, mani@kernel.org,
michael.riesch@collabora.com, jacopo.mondi@ideasonboard.com,
nicholas@rothemail.net, benjamin.mugnier@foss.st.com,
sylvain.petinot@foss.st.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] media: i2c: Add missing v4l2_subdev_cleanup() calls
Date: Wed, 9 Sep 2026 11:02:22 +0300 [thread overview]
Message-ID: <cover.1788940469.git.chubuchnyi@gmail.com> (raw)
v4l2_subdev_init_finalize() allocates the subdev active state and only
v4l2_subdev_cleanup() frees it. These five drivers never call it, so they
leak the state on every unbind.
Separate patches because the Fixes tags span 2022 to 2023 and go to
different stable trees. The st-mipid02 one dates from the active state
conversion, not from the original driver.
Aleksandr Chubuchnyi (5):
media: i2c: imx296: Add missing v4l2_subdev_cleanup() call
media: i2c: imx415: Add missing v4l2_subdev_cleanup() call
media: i2c: mt9m114: Add missing v4l2_subdev_cleanup() calls
media: i2c: ov8858: Add missing v4l2_subdev_cleanup() call
media: i2c: st-mipid02: Add missing v4l2_subdev_cleanup() call
drivers/media/i2c/imx296.c | 1 +
drivers/media/i2c/imx415.c | 1 +
drivers/media/i2c/mt9m114.c | 2 ++
drivers/media/i2c/ov8858.c | 2 ++
drivers/media/i2c/st-mipid02.c | 2 ++
5 files changed, 8 insertions(+)
--
2.43.0
next reply other threads:[~2026-09-09 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:02 Aleksandr Chubuchnyi [this message]
2026-09-09 8:02 ` [PATCH 1/5] media: i2c: imx296: Add missing v4l2_subdev_cleanup() call Aleksandr Chubuchnyi
2026-09-09 8:02 ` [PATCH 2/5] media: i2c: imx415: " Aleksandr Chubuchnyi
2026-09-09 8:02 ` [PATCH 3/5] media: i2c: mt9m114: Add missing v4l2_subdev_cleanup() calls Aleksandr Chubuchnyi
2026-09-09 8:02 ` [PATCH 4/5] media: i2c: ov8858: Add missing v4l2_subdev_cleanup() call Aleksandr Chubuchnyi
2026-09-09 8:02 ` [PATCH 5/5] media: i2c: st-mipid02: " Aleksandr Chubuchnyi
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=cover.1788940469.git.chubuchnyi@gmail.com \
--to=chubuchnyi@gmail.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@collabora.com \
--cc=nicholas@rothemail.net \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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®