From: Seifelden Abdelmonem <saif.elden.hatim@gmail.com>
To: Caspar Adriani <caspar.adriani@proton.me>
Cc: Bin Du <bin.du@amd.com>,
Nirujogi Pratap <pratap.nirujogi@amd.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Benjamin Chan <benjamin.chan@amd.com>, King Li <King.Li@amd.com>,
Yifei Gao <gyf161023@gmail.com>,
Sultan Alsawaf <sultan@kerneltoast.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Seifelden Abdelmonem <saif.elden.hatim@gmail.com>
Subject: Re: [PATCH] media: amd: isp4: fix self-deadlock in isp4sd_start_stream() error path
Date: Tue, 3 Nov 2026 18:27:07 +0300 [thread overview]
Message-ID: <20261103152707.90152-1-saif.elden.hatim@gmail.com> (raw)
In-Reply-To: <20261028-isp4-start-stream-deadlock-v1-1-babd80273148@proton.me>
Tested on an ASUS ROG Flow Z13 (GZ302EA) with v7.2.10 and an
out-of-tree setup in which the OV13B10 streams (NV12 1920x1080), with
this patch applied on top of my two isp4 fixes [1]:
- stream with the format set: 90 frames;
- stop, then stream again without setting the format: VIDIOC_STREAMON
returns -EINVAL after "fail to get out prop" and "fail to setup
output", v4l2-ctl exits and no task is left blocked;
- stream with the format set again: 90 frames.
No hung task, oops or WARN in the kernel log. I did not run the
sequence without the patch on this setup.
Tested-by: Seifelden Abdelmonem <saif.elden.hatim@gmail.com>
[1] https://lore.kernel.org/all/20261026182442.229869-1-saif.elden.hatim@gmail.com/
Regards,
Seifelden
prev parent reply other threads:[~2026-11-03 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 14:05 Caspar Adriani via B4 Relay
2026-10-28 18:52 ` Sultan Alsawaf
2026-10-30 2:09 ` Bin Du
2026-11-02 19:19 ` Nirujogi, Pratap
2026-11-03 15:27 ` Seifelden Abdelmonem [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=20261103152707.90152-1-saif.elden.hatim@gmail.com \
--to=saif.elden.hatim@gmail.com \
--cc=King.Li@amd.com \
--cc=benjamin.chan@amd.com \
--cc=bin.du@amd.com \
--cc=caspar.adriani@proton.me \
--cc=gyf161023@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pratap.nirujogi@amd.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=sultan@kerneltoast.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
all inboxes | Powered by JetHome®