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 3/3] media: ipu6: Check the ipu7 output pin queue before completing a buffer
Date: Tue, 29 Sep 2026 15:37:31 +0100 [thread overview]
Message-ID: <20260929143731.43358-4-devnexen@gmail.com> (raw)
In-Reply-To: <20260929143731.43358-1-devnexen@gmail.com>
A PIN_DATA_READY response for an unconfigured pin dereferences a NULL
output_pins_queue entry in interrupt context. Check the queue like the
ipu6 path does.
Fixes: f268203d74ff ("media: ipu6: Add ipu7 isr handler")
Signed-off-by: David Carlier <devnexen@gmail.com>
---
drivers/media/pci/intel/ipu6/ipu7-fw-isys.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/pci/intel/ipu6/ipu7-fw-isys.c b/drivers/media/pci/intel/ipu6/ipu7-fw-isys.c
index 379a84b595fd..d92d4cad30e6 100644
--- a/drivers/media/pci/intel/ipu6/ipu7-fw-isys.c
+++ b/drivers/media/pci/intel/ipu6/ipu7-fw-isys.c
@@ -644,7 +644,8 @@ static int ipu7_isys_isr_one(struct ipu6_bus_device *adev)
struct isys_fw_msgs, dummy);
ipu6_put_fw_msg_buf(ipu6_bus_get_drvdata(adev), isys_fw_msg);
- if (resp->pin_id < IPU6_ISYS_OUTPUT_PINS)
+ if (resp->pin_id < IPU6_ISYS_OUTPUT_PINS &&
+ stream->output_pins_queue[resp->pin_id])
ipu6_stream_buf_ready(stream, resp->pin_id,
resp->pin.addr, ts, 0);
else
--
2.55.0
prev parent 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 [PATCH v2 0/3] media: ipu6: ipu7 and ipu6 fw-isys fixes David Carlier
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 ` David Carlier [this message]
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-4-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.