From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Stefan Schmidt <stefan.schmidt@linaro.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Wangao Wang <wangao.wang@oss.qualcomm.com>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] Revert "media: iris: Add sanity check for stop streaming"
Date: Mon, 5 Jan 2026 12:50:57 +0000 [thread overview]
Message-ID: <69aaa79f-27ce-4308-aecb-260b50bcd0d6@linaro.org> (raw)
In-Reply-To: <a899436d-d14e-bd16-7727-e342fcd02de6@oss.qualcomm.com>
On 05/01/2026 09:51, Dikshita Agarwal wrote:
>
>
> On 12/30/2025 3:55 PM, Bryan O'Donoghue wrote:
>> On 29/12/2025 06:31, Dikshita Agarwal wrote:
>>> Revert the check that skipped stop_streaming when the instance was in
>>> IRIS_INST_ERROR, as it caused multiple regressions:
>>>
>>> 1. Buffers were not returned to vb2 when the instance was already in
>>> error state, triggering warnings in the vb2 core because buffer
>>> completion was skipped.
>>>
>>> 2. If a session failed early (e.g. unsupported configuration), the
>>> instance transitioned to IRIS_INST_ERROR. When userspace attempted
>>> to stop streaming for cleanup, stop_streaming was skipped due to the
>>> added check, preventing proper teardown and leaving the firmware
>>> in an inconsistent state.
>>>
>>> Fixes: ad699fa78b59 ("media: iris: Add sanity check for stop streaming")
>>> Signed-off-by: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
>>> ---
>>> drivers/media/platform/qcom/iris/iris_vb2.c | 8 +++-----
>>> 1 file changed, 3 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/media/platform/qcom/iris/iris_vb2.c
>>> b/drivers/media/platform/qcom/iris/iris_vb2.c
>>> index
>>> db8768d8a8f61c9ceb04e423d0a769d35114e20e..139b821f7952feb33b21a7045aef9e8a4782aa3c 100644
>>> --- a/drivers/media/platform/qcom/iris/iris_vb2.c
>>> +++ b/drivers/media/platform/qcom/iris/iris_vb2.c
>>> @@ -231,8 +231,6 @@ void iris_vb2_stop_streaming(struct vb2_queue *q)
>>> return;
>>> mutex_lock(&inst->lock);
>>> - if (inst->state == IRIS_INST_ERROR)
>>> - goto exit;
>>> if (!V4L2_TYPE_IS_OUTPUT(q->type) &&
>>> !V4L2_TYPE_IS_CAPTURE(q->type))
>>> @@ -243,10 +241,10 @@ void iris_vb2_stop_streaming(struct vb2_queue *q)
>>> goto exit;
>>> exit:
>>> - if (ret) {
>>> - iris_helper_buffers_done(inst, q->type, VB2_BUF_STATE_ERROR);
>>> + iris_helper_buffers_done(inst, q->type, VB2_BUF_STATE_ERROR);
>>> + if (ret)
>>> iris_inst_change_state(inst, IRIS_INST_ERROR);
>>> - }
>>> +
>>> mutex_unlock(&inst->lock);
>>> }
>>>
>>
>> This revert looks strange, should be something like:
>>
>> commit 9b6b11d31918722b4522b8982141d7b9646c0e48 (HEAD -> next-6.19-camss-v2)
>> Author: Bryan O'Donoghue <bod@kernel.org>
>> Date: Tue Dec 30 10:20:01 2025 +0000
>>
>> Revert "media: iris: Add sanity check for stop streaming"
>>
>> This reverts commit ad699fa78b59241c9d71a8cafb51525f3dab04d4.
>>
>> Everything is broken I give up.
>>
>> Signed-off-by: Bryan O'Donoghue <bod@kernel.org>
>>
>> diff --git a/drivers/media/platform/qcom/iris/iris_vb2.c
>> b/drivers/media/platform/qcom/iris/iris_vb2.c
>> index db8768d8a8f61..139b821f7952f 100644
>> --- a/drivers/media/platform/qcom/iris/iris_vb2.c
>> +++ b/drivers/media/platform/qcom/iris/iris_vb2.c
>> @@ -231,8 +231,6 @@ void iris_vb2_stop_streaming(struct vb2_queue *q)
>> return;
>>
>> mutex_lock(&inst->lock);
>> - if (inst->state == IRIS_INST_ERROR)
>> - goto exit;
>>
>> if (!V4L2_TYPE_IS_OUTPUT(q->type) &&
>> !V4L2_TYPE_IS_CAPTURE(q->type))
>> @@ -243,10 +241,10 @@ void iris_vb2_stop_streaming(struct vb2_queue *q)
>> goto exit;
>>
>> exit:
>> - if (ret) {
>> - iris_helper_buffers_done(inst, q->type, VB2_BUF_STATE_ERROR);
>> + iris_helper_buffers_done(inst, q->type, VB2_BUF_STATE_ERROR);
>> + if (ret)
>> iris_inst_change_state(inst, IRIS_INST_ERROR);
>> - }
>> +
>> mutex_unlock(&inst->lock);
>> }
>>
>> Just `git revert ad699fa78b59241c9d71a8cafb51525f3dab04d4` and add your
>> commit log ?!
>
> Yeah I did the same, revert and changed the commit message.
>
> BTW, I don't see any difference in my change and your commit, anything I am
> missing here?
Take this example, I believe the "This reverts commit xxx" is added by
the revert command and its best practice to include it.
commit afb9917d9b374ecb77d478c2a052e20875c6e232
Author: Christian Brauner <brauner@kernel.org>
Date: Fri Dec 5 13:50:31 2025 +0100
Revert "net/socket: convert sock_map_fd() to FD_ADD()"
This reverts commit 245f0d1c622b0183ce4f44b3e39aeacf78fae594.
I can just add it back in with the PR though its NBD.
---
bod
next prev parent reply other threads:[~2026-01-05 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 6:31 [PATCH v2 0/6] media: iris: misc fixes for fluster, seek and concurrency issues Dikshita Agarwal
2025-12-29 6:31 ` [PATCH v2 1/6] media: iris: Add buffer to list only after successful allocation Dikshita Agarwal
2026-01-07 10:26 ` Vikash Garodia
2025-12-29 6:31 ` [PATCH v2 2/6] media: iris: Skip resolution set on first IPSC Dikshita Agarwal
2026-01-07 10:27 ` Vikash Garodia
2025-12-29 6:31 ` [PATCH v2 3/6] media: iris: gen1: Destroy internal buffers after FW releases Dikshita Agarwal
2026-01-07 10:27 ` Vikash Garodia
2025-12-29 6:31 ` [PATCH v2 4/6] Revert "media: iris: Add sanity check for stop streaming" Dikshita Agarwal
2025-12-30 10:25 ` Bryan O'Donoghue
2026-01-05 9:51 ` Dikshita Agarwal
2026-01-05 12:50 ` Bryan O'Donoghue [this message]
2026-01-06 5:47 ` Dikshita Agarwal
2026-01-07 10:29 ` Vikash Garodia
2025-12-29 6:31 ` [PATCH v2 5/6] media: iris: gen2: Add sanity check for session stop Dikshita Agarwal
2025-12-30 10:33 ` Bryan O'Donoghue
2026-01-07 10:06 ` Dikshita Agarwal
2026-01-12 11:09 ` Vikash Garodia
2025-12-29 6:31 ` [PATCH v2 6/6] media: iris: Prevent output buffer queuing before stream-on completes Dikshita Agarwal
2026-01-12 11:09 ` Vikash Garodia
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=69aaa79f-27ce-4308-aecb-260b50bcd0d6@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=hverkuil+cisco@kernel.org \
--cc=hverkuil@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stefan.schmidt@linaro.org \
--cc=vikash.garodia@oss.qualcomm.com \
--cc=wangao.wang@oss.qualcomm.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