From: Biren Pandya <birenpandya@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Biren Pandya <birenpandya@gmail.com>
Subject: [PATCH 0/2] media: i2c: ov7740: Fix remove() teardown and PM runtime
Date: Tue, 16 Jun 2026 02:34:10 +0530 [thread overview]
Message-ID: <20260615210412.34567-1-birenpandya@gmail.com> (raw)
This series addresses two severe issues in the teardown path of the
ov7740 image sensor driver.
The first patch addresses a kernel panic caused by a use-after-destroy
on the driver's mutex, exacerbated by a double-free of both the mutex
and the V4L2 control handler.
The second patch modernizes the runtime PM sleep sequence by properly
checking the return value of PM wake operations before issuing I2C
power down sequences, preventing unbalanced PM tracking or hangs on
disconnected devices.
Biren Pandya (2):
media: i2c: ov7740: Fix use-after-destroy in remove()
media: i2c: ov7740: Fix unchecked pm_runtime_get_sync() in remove()
drivers/media/i2c/ov7740.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-06-15 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 21:04 Biren Pandya [this message]
2026-06-15 21:04 ` [PATCH 1/2] media: i2c: ov7740: Fix use-after-destroy in remove() Biren Pandya
2026-07-08 8:59 ` Sakari Ailus
2026-06-15 21:04 ` [PATCH 2/2] media: i2c: ov7740: Fix unchecked pm_runtime_get_sync() " Biren Pandya
2026-07-08 8:46 ` Sakari Ailus
[not found] ` <20260708125720.27156-4-birenpandya@gmail.com>
2026-07-08 12:57 ` [PATCH v2 1/2] media: i2c: ov7740: fix unbalanced pm_runtime_get_sync in remove Biren Pandya
2026-07-08 12:57 ` [PATCH v2 2/2] media: i2c: ov7740: fix use-after-destroy " 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=20260615210412.34567-1-birenpandya@gmail.com \
--to=birenpandya@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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