From: Niharika Khare <niharikakhare2101@gmail.com>
To: sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [PATCH] media: mc: Remove spurious WARN_ON in __media_pipeline_start
Date: Fri, 21 Aug 2026 22:28:07 +0530 [thread overview]
Message-ID: <20260821165833.10042-1-niharikakhare2101@gmail.com> (raw)
Vimc driver's entity topology has three capture nodes and two of
those (Raw Capture 0 and RGB/YUV Capture) are reachable from each
other via enabled links. The crash report and the C repro show that
the two capture nodes attempt to invoke a STREAMON session one after
the other, which resulted in the WARNING getting triggered by the
media controller.
vimc link validate: Sensor A:src:640x480 (0x42474752, 0, 0, 0, 0) Raw Capture 0:snk:640x480 (0x42474752, 8, 0, 0, 0)
vimc link validate: Scaler:src:640x480 (0x33424752, 8, 0, 0, 0) RGB/YUV Capture:snk:640x480 (0x33424752, 8, 0, 0, 0)
origin->pipe && origin->pipe != pipe
WARNING: drivers/media/mc/mc-entity.c:785 at __media_pipeline_start+0x1add/0x22b0, CPU#1: syz.0.17/5912
The graph walk originating from Raw Capture 0 (first STREAMON in C
repro on /dev/video0) reaches RGB/YUV Capture and marks its origin
pad's pipe with its own pipe. When RGB/YUV Capture's graph walk starts
(second STREAMON in C repro on /dev/video4), the pad is already
claimed. This is a legitimate userspace request but not something that
kernel should allow while the pad remains claimed. Hence, the kernel
checks the pipe and returns -EBUSY instead of raising a bug, same as
the other non-origin pads. The check on origin pad's pipe needs to stay
otherwise the origin pad case would go through the increment on the
start_count path, even though there exists a loop few lines below this
block to check the pad and return -EBUSY. The check also provides early
failure detection and prevents the complete graph walk.
Fixes: ae219872834a ("media: mc: entity: Rewrite media_pipeline_start()")
Reported-by: syzbot+68e901d044baaea1f60c@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=68e901d044baaea1f60c
Tested-by: syzbot+68e901d044baaea1f60c@syzkaller.appspotmail.com
Signed-off-by: Niharika Khare <niharikakhare2101@gmail.com>
---
drivers/media/mc/mc-entity.c | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/media/mc/mc-entity.c b/drivers/media/mc/mc-entity.c
index 3fa0bc687..7b4ef2c95 100644
--- a/drivers/media/mc/mc-entity.c
+++ b/drivers/media/mc/mc-entity.c
@@ -778,12 +778,18 @@ __must_check int __media_pipeline_start(struct media_pad *origin,
lockdep_assert_held(&mdev->graph_mutex);
- /*
- * If the pad is already part of a pipeline, that pipeline must be the
- * same as the pipe given to media_pipeline_start().
- */
- if (WARN_ON(origin->pipe && origin->pipe != pipe))
- return -EINVAL;
+ /*
+ * If the pad is part of a different pipeline than the one passed on to
+ * media_pipeline_start(), the pad must wait for the ongoing session on
+ * this previous pipeline to complete before it starts a new session.
+ * The request for starting the pipeline, although valid, cannot be
+ * served until the ongoing request finishes.
+ */
+ if (origin->pipe && origin->pipe != pipe) {
+ dev_dbg(mdev->dev, "Failed to start pipeline: pad '%s':%u busy\n",
+ origin->entity->name, origin->index);
+ return -EBUSY;
+ }
/*
* If the pipeline has already been started, it is guaranteed to be
--
2.53.0
next reply other threads:[~2026-08-21 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:58 Niharika Khare [this message]
2026-08-21 19:33 ` [PATCH] media: mc: Remove spurious WARN_ON in __media_pipeline_start Laurent Pinchart
2026-08-22 4:23 ` Niharika Khare
2026-08-31 8:20 ` Niharika Khare
2026-09-10 9:41 ` Niharika Khare
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=20260821165833.10042-1-niharikakhare2101@gmail.com \
--to=niharikakhare2101@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=syzkaller-bugs@googlegroups.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.