From: David Carlier <devnexen@gmail.com>
To: linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Antti Laakso <antti.laakso@linux.intel.com>,
Sarang Sapre <sarang.sapre@intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
linux-kernel@vger.kernel.org, David Carlier <devnexen@gmail.com>
Subject: [PATCH v2 0/3] media: ipu6: ipu7 and ipu6 fw-isys fixes
Date: Tue, 29 Sep 2026 15:37:28 +0100 [thread overview]
Message-ID: <20260929143731.43358-1-devnexen@gmail.com> (raw)
Fix the firmware config leaks on every stream start in both the ipu7 and
ipu6 fw-isys init paths, and a NULL dereference on a PIN_DATA_READY
response for an unconfigured ipu7 output pin.
Changes in v2:
- 1/3: use goto labels for error handling (Sakari)
- 2/3: new, same leak in ipu6_isys_fwcom_cfg_init() (Sakari), also check
its return value
- 3/3: unchanged
v1: https://lore.kernel.org/linux-media/20260927201631.153126-1-devnexen@gmail.com/
David Carlier (3):
media: ipu6: Fix ipu7 firmware context leak on stream start
media: ipu6: Fix firmware config leak on stream start
media: ipu6: Check the ipu7 output pin queue before completing a
buffer
drivers/media/pci/intel/ipu6/ipu6-fw-isys.c | 34 +++++++++++++++------
drivers/media/pci/intel/ipu6/ipu7-fw-isys.c | 26 ++++++++++------
2 files changed, 41 insertions(+), 19 deletions(-)
base-commit: 2dcdfb625c3b8fe87454e19dfbc54b3e3f0ad70e
--
2.55.0
next reply other threads:[~2026-09-29 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 14:37 David Carlier [this message]
2026-09-29 14:37 ` [PATCH v2 1/3] media: ipu6: Fix ipu7 firmware context leak on stream start David Carlier
2026-09-29 14:37 ` [PATCH v2 2/3] media: ipu6: Fix firmware config " David Carlier
2026-09-29 14:37 ` [PATCH v2 3/3] media: ipu6: Check the ipu7 output pin queue before completing a buffer David Carlier
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=20260929143731.43358-1-devnexen@gmail.com \
--to=devnexen@gmail.com \
--cc=antti.laakso@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sarang.sapre@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 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.