From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: venus: fix duplicated code for different branches
Date: Fri, 18 Aug 2017 10:55:43 -0500 [thread overview]
Message-ID: <96fa5d72-66d1-d28e-5d9f-d991e0c1ce83@embeddedor.com> (raw)
In-Reply-To: <99a35cad-9152-ec15-7843-de4668a9190f@linaro.org>
Hi Stanimir,
On 08/18/2017 02:52 AM, Stanimir Varbanov wrote:
> Hi Gustavo,
>
> On 08/18/2017 02:12 AM, Gustavo A. R. Silva wrote:
>> Refactor code in order to avoid identical code for different branches.
>>
>> This issue was detected with the help of Coccinelle.
>>
>> Addresses-Coverity-ID: 1415317
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>> ---
>> This code was reported by Coverity and it was tested by compilation only.
>> Please, verify if this is an actual bug.
>
> Yes looks like copy/paste error, and yes it is a bug.
>
Thank you for reviewing it.
>>
>> drivers/media/platform/qcom/venus/helpers.c | 6 +-----
>> 1 file changed, 1 insertion(+), 5 deletions(-)
>>
>> diff --git a/drivers/media/platform/qcom/venus/helpers.c b/drivers/media/platform/qcom/venus/helpers.c
>> index 5f4434c..8a5c467 100644
>> --- a/drivers/media/platform/qcom/venus/helpers.c
>> +++ b/drivers/media/platform/qcom/venus/helpers.c
>> @@ -240,11 +240,7 @@ static void return_buf_error(struct venus_inst *inst,
>> {
>> struct v4l2_m2m_ctx *m2m_ctx = inst->m2m_ctx;
>>
>> - if (vbuf->vb2_buf.type == V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE)
>> - v4l2_m2m_src_buf_remove_by_buf(m2m_ctx, vbuf);
>> - else
>> - v4l2_m2m_src_buf_remove_by_buf(m2m_ctx, vbuf);
>
> the correct fix must replace the second v4l2_m2m_src_* with v4l2_m2m_dst_*.
>
I'll send a patch to fix this bug shortly
>> -
>> + v4l2_m2m_src_buf_remove_by_buf(m2m_ctx, vbuf);
>> v4l2_m2m_buf_done(vbuf, VB2_BUF_STATE_ERROR);
>> }
>>
>>
>
Thanks!
--
Gustavo A. R. Silva
next prev parent reply other threads:[~2017-08-18 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 23:12 [PATCH] media: venus: fix duplicated code for different branches Gustavo A. R. Silva
2017-08-18 6:57 ` Hans Verkuil
2017-08-18 7:52 ` Stanimir Varbanov
2017-08-18 15:55 ` Gustavo A. R. Silva [this message]
2017-08-18 16:07 ` [PATCH v2] venus: fix copy/paste error in return_buf_error Gustavo A. R. Silva
2017-08-21 9:14 ` Stanimir Varbanov
2017-08-22 19:22 ` Gustavo A. R. Silva
2017-08-23 12:59 ` Stanimir Varbanov
2017-08-23 15:14 ` Stanimir Varbanov
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=96fa5d72-66d1-d28e-5d9f-d991e0c1ce83@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stanimir.varbanov@linaro.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