From: Greg KH <gregkh@linuxfoundation.org>
To: Saikiran <bjsaikiran@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] media: qcom: camss: Fix pipeline lock leak in stop_streaming
Date: Sun, 25 Jan 2026 16:01:35 +0100 [thread overview]
Message-ID: <2026012527-maker-deplored-0884@gregkh> (raw)
In-Reply-To: <20260125145544.50785-2-bjsaikiran@gmail.com>
On Sun, Jan 25, 2026 at 08:25:43PM +0530, Saikiran wrote:
> When a browser or application closes the camera, if any subdevice fails
> to stop streaming, video_stop_streaming() returns early without calling
> video_device_pipeline_stop(). This leaves the pipeline permanently locked,
> preventing any future camera access until reboot.
>
> Fix this by logging errors but continuing to stop all remaining subdevices
> and always releasing the pipeline lock, even when errors occur during the
> stop sequence.
>
> Fixes: 89013969e232 ("media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels")
> Cc: stable@vger.kernel.org
> Tested-on: Lenovo Yoga Slim 7x (Snapdragon X Elite, ov02c10 camera)
> Signed-off-by: Saikiran <bjsaikiran@gmail.com>
> ---
> drivers/media/platform/qcom/camss/camss-video.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/platform/qcom/camss/camss-video.c b/drivers/media/platform/qcom/camss/camss-video.c
> index 831486e14754..242c44f97801 100644
> --- a/drivers/media/platform/qcom/camss/camss-video.c
> +++ b/drivers/media/platform/qcom/camss/camss-video.c
> @@ -312,9 +312,15 @@ static void video_stop_streaming(struct vb2_queue *q)
>
> ret = v4l2_subdev_call(subdev, video, s_stream, 0);
>
> + /*
> + * Don't return early on error - we must continue to stop
> + * remaining subdevices and release the pipeline lock to
> + * prevent the camera from being permanently locked.
> + */
> if (ret) {
> - dev_err(video->camss->dev, "Video pipeline stop failed: %d\n", ret);
> - return;
> + dev_err(video->camss->dev,
> + "Failed to stop subdev '%s': %d\n",
> + subdev->name, ret);
> }
> }
>
> --
> 2.51.0
>
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2026-01-25 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260125145544.50785-1-bjsaikiran@gmail.com>
2026-01-25 14:55 ` [PATCH 1/2] media: qcom: camss: Fix pipeline lock leak in stop_streaming Saikiran
2026-01-25 15:01 ` Greg KH [this message]
2026-01-25 14:55 ` [PATCH 2/2] media: i2c: ov02c10: Check for errors in disable_streams Saikiran
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=2026012527-maker-deplored-0884@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bjsaikiran@gmail.com \
--cc=stable@vger.kernel.org \
/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