From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [bug report] [media] s5p-mfc: use MFC_BUF_FLAG_EOS to identify last buffers in decoder capture queue
Date: Fri, 5 Apr 2019 14:33:31 +0300 [thread overview]
Message-ID: <20190405113331.GU32613@kadam> (raw)
In-Reply-To: <f38dbe7a-d4b1-b012-d667-eaaade6e9ff6@samsung.com>
On Fri, Apr 05, 2019 at 12:02:49PM +0200, Andrzej Hajda wrote:
> Hi Dan,
>
> On 04.04.2019 17:42, Dan Carpenter wrote:
> > Hello Andrzej Hajda,
> >
> > The patch 4d0b0ed63660: "[media] s5p-mfc: use MFC_BUF_FLAG_EOS to
> > identify last buffers in decoder capture queue" from Oct 7, 2015,
> > leads to the following static checker warning:
> >
> > drivers/media/platform/s5p-mfc/s5p_mfc_dec.c:664 vidioc_dqbuf()
> > warn: uncapped user index 'ctx->dst_bufs[buf->index]'
>
>
> Almost identical e-mail you have sent about year ago, and me and Hans
> have explained you that it is false positive.
>
> Has something changed?
Wow! It's remarkable how similar the emails are. Thank you for
your patience on this. I am testing a patch which should silence this
false positive in Smatch.
regards,
dan carpenter
next prev parent reply other threads:[~2019-04-05 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190404154231epcas4p11c6ce6ab44d5b61c66e246fab78972e9@epcas4p1.samsung.com>
2019-04-04 15:42 ` [bug report] [media] s5p-mfc: use MFC_BUF_FLAG_EOS to identify last buffers in decoder capture queue Dan Carpenter
2019-04-05 10:02 ` Andrzej Hajda
2019-04-05 11:33 ` Dan Carpenter [this message]
[not found] <CGME20180123083259epcas3p1fb9a8b4e4ad34eb245fca67d4204cba4@epcas3p1.samsung.com>
2018-01-23 8:32 ` Dan Carpenter
2018-01-25 9:58 ` Andrzej Hajda
2018-01-25 10:14 ` Hans Verkuil
2018-01-25 12:25 ` Dan Carpenter
2018-01-25 12:31 ` Hans Verkuil
2018-01-25 13:10 ` Dan Carpenter
2018-01-25 12:46 ` Andrzej Hajda
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=20190405113331.GU32613@kadam \
--to=dan.carpenter@oracle.com \
--cc=a.hajda@samsung.com \
--cc=linux-media@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 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.