Linux Media Controller development
 help / color / mirror / Atom feed
From: Nicola Fiorillo <nicfio@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, dongcheng.yan@intel.com,
	mehdi.djait@linux.intel.com, ong.hock.yu@intel.com,
	khai.wen.ng@intel.com, antti.laakso@linux.intel.com,
	manik.bajpai@intel.com, divyamani.tripathi@intel.com,
	nicfio@gmail.com
Subject: Re: [PATCH v2 09/21] media: ipu6: Start streaming once all streams have started, stop when not
Date: Fri, 18 Sep 2026 09:36:19 +0200	[thread overview]
Message-ID: <178971697984.34231.15295000197727096742@gmail.com> (raw)
In-Reply-To: <20260917113923.59004-10-sakari.ailus@linux.intel.com>

Hi Sakari,

On Thu, Sep 17, 2026 at 02:39:11PM +0300, Sakari Ailus wrote:
> +static bool ipu6_isys_csi2_streaming_change(struct ipu6_isys_subdev *asd,
> +					    struct v4l2_subdev_state *state,
> +					    u32 pad, u8 *vc, bool enable)

Four things in this function, all found by reading it. I cannot build or
test a kernel at the moment, so please take this as review and nothing
more; none of it is reproduced on hardware.

1) The error return does not fit the return type.

> +	ret = v4l2_subdev_call(remote_sd, pad, get_frame_desc,
> +			       remote_pad->index, &desc);
> +	if (ret)
> +		return ret;

The function returns bool, so a negative errno from get_frame_desc()
becomes true, and both callers read true as "go ahead and change the
streaming state". In ipu6_isys_csi2_enable_streams() that starts the
firmware stream and then runs

	csi2->streaming_vc |= BIT(vc);

with vc still uninitialised: *vc is assigned only at the end of the
function, past this early return. ipu6_isys_csi2_disable_streams() does
the mirror of it with &= ~BIT(vc). The two "return false" exits are
fine, they make the caller skip the change; only this one carries a
value.

2) media_pad_remote_pad_unique() never returns NULL, so the guard below
   it is dead code.

> +		struct media_pad *video_pad =
> +			media_pad_remote_pad_unique(&asd->sd.entity.pads[route->source_pad]);
> +		struct ipu6_isys_video *av = !video_pad ? NULL :
> +			container_of_const(video_pad,
> +					   struct ipu6_isys_video, pad);
> +
> +		if (!av) {

It returns ERR_PTR(-ENOLINK) when no enabled link is found and
ERR_PTR(-ENOTUNIQ) when there is more than one. !video_pad is therefore
never true, the dev_dbg() below is unreachable, and the error pointer
goes into container_of_const() instead -- where av->streaming, a few
lines further down, dereferences it.

IS_ERR() is what the check wants. This same file already does it that
way, in ipu6_isys_csi2_get_link_freq():

	src_pad = media_pad_remote_pad_unique(...);
	if (IS_ERR(src_pad)) {
		dev_err(&csi2->isys->adev->auxdev.dev,
			"can't get source pad of %s (%pe)\n",
			csi2->asd.sd.name, src_pad);
		return PTR_ERR(src_pad);
	}

3) The lookup on the sink pad, higher up in the same function, has no
   check at all:

> +	struct media_pad *remote_pad =
> +		media_pad_remote_pad_unique(&asd->sd.entity.pads[this_route->sink_pad]);
> +	struct v4l2_subdev *remote_sd =
> +		media_entity_to_v4l2_subdev(remote_pad->entity);

remote_pad->entity is read immediately, so the same error pointer is
dereferenced here, with no guard to correct.

4) Unless I am misreading it, the inner lookup in the loop does not
   depend on the loop variable:

> +	for_each_active_route(&state->routing, route) {
> +		struct v4l2_mbus_frame_desc_entry *entry = NULL;
> +
> +		for (unsigned int i = 0; i < desc.num_entries; i++) {
> +			if (desc.entry[i].stream == this_entry->stream) {
> +				entry = &desc.entry[i];
> +				break;
> +			}
> +		}
> +
> +		if (entry->bus.csi2.vc != this_entry->bus.csi2.vc)
> +			continue;

The search key is this_entry->stream, which does not change across
iterations, so entry always ends up as this_entry itself and the vc
comparison can never differ. The "continue" is never taken and every
active route is counted, whatever its virtual channel. Going by the
commit message, the key here was meant to be route->sink_stream.

Finally, a note rather than a request. After the whole series,
ipu6_isys_csi2_enable_streams() and ipu6_isys_csi2_disable_streams()
still call media_pad_remote_pad_first() on the sink pad and dereference
the result unchecked -- and that one does return NULL. It is what my
[PATCH v2 1/3] touched. I have dropped that patch and I am not
reopening the question of the scenario behind it; I mention it only
because if the checks in 2) and 3) go in, that pointer is sitting right
next to them.

Thanks,

-- 
Nicola Fiorillo

  reply	other threads:[~2026-09-18  7:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 11:39 [PATCH v2 00/21] IPU6 multi-stream and metadata support preparation Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 01/21] media: ipu6: Fix releasing resources at failing streamon Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 02/21] media: ipu6: Move streaming control to CSI-2 receiver driver Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 03/21] media: ipu6: Stream number on CSI-2 receiver source pads is always 0 Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 04/21] media: ipu6: Rename misnamed out_free_watermark label in video init Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 05/21] media: ipu6: Always request a capture ack Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 06/21] media: ipu6: Clean up link frequency calculation Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 07/21] media: ipu6: Get watermark configuration directly from ipdata Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 08/21] media: ipu6: Collect IPU streams into CSI-2 receiver sub-device context Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 09/21] media: ipu6: Start streaming once all streams have started, stop when not Sakari Ailus
2026-09-18  7:36   ` Nicola Fiorillo [this message]
2026-09-18 20:56     ` Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 10/21] media: ipu6: Add lockdep checks for CSI-2 streaming enable and disable Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 11/21] media: ipu6: Remove nr_queues and nr_streaming fields in ipu6_isys_stream Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 12/21] media: ipu6: Collect enabled stream IDs Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 13/21] media: ipu6: Avoid accessing av->streams before streaming Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 14/21] media: ipu6: Rework watermark calculation Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 15/21] media: ipu6: Rework watermark setting Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 16/21] media: ipu6: Bridge the gap between streams in V4L2 and IPU6 firmware Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 17/21] media: ipu6: Drop {get,put}_streams_opened() Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 18/21] media: ipu6: Serialise access to stream pointers by isys stream_lock Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 19/21] media: ipu6: Move firmware init/cleanup to RPM callbacks Sakari Ailus
2026-09-17 11:39 ` [PATCH v2 20/21] media: ipu6: Don't track power status, rely on runtime PM Sakari Ailus
2026-09-22  9:16   ` Manik Bajpai
2026-09-17 11:39 ` [PATCH v2 21/21] media: ipu6: Support upstream sub-devices without get_frame_desc() Sakari Ailus

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=178971697984.34231.15295000197727096742@gmail.com \
    --to=nicfio@gmail.com \
    --cc=antti.laakso@linux.intel.com \
    --cc=divyamani.tripathi@intel.com \
    --cc=dongcheng.yan@intel.com \
    --cc=khai.wen.ng@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=manik.bajpai@intel.com \
    --cc=mehdi.djait@linux.intel.com \
    --cc=ong.hock.yu@intel.com \
    --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