From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] media: vsp1: cleanup a false positive warning
Date: Wed, 8 Aug 2018 10:58:20 -0300 [thread overview]
Message-ID: <20180808105820.67469806@coco.lan> (raw)
In-Reply-To: <20180507122103.40048014@vento.lan>
Em Mon, 7 May 2018 12:21:03 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> Em Mon, 07 May 2018 17:05:24 +0300
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
>
> > Hi Mauro,
> >
> > Thank you for the patch.
> >
> > On Friday, 4 May 2018 15:13:58 EEST Mauro Carvalho Chehab wrote:
> > > With the new vsp1 code changes introduced by changeset
> > > f81f9adc4ee1 ("media: v4l: vsp1: Assign BRU and BRS to pipelines
> > > dynamically"), smatch complains with:
> > > drivers/media/platform/vsp1/vsp1_drm.c:262 vsp1_du_pipeline_setup_bru()
> > > error: we previously assumed 'pipe->bru' could be null (see line 180)
> > >
> > > This is a false positive, as, if pipe->bru is NULL, the brx
> > > var will be different, with ends by calling a code that will
> > > set pipe->bru to another value.
> > >
> > > Yet, cleaning this false positive is as easy as adding an explicit
> > > check if pipe->bru is NULL.
> >
> > It's not very difficult indeed, but it really is a false positive. I think the
> > proposed change decreases readability, the condition currently reads as "if
> > (new brx != old brx)", why does smatch even flag that as an error ?
>
> I've no idea. Never studied smatch code. If you don't think that
> this is a fix for it, do you have an alternative patch (either to
> smatch or to vsp1)?
Ping.
We're carrying this warning since the latest Kernel release. If you
don't have a better fix, let's apply it for 4.19. You may work on
a different solution if you think you'll be able to either patch
smatch in order to identify such complex logic or do something else
at the vsp1 code to simplify the logic on future Kernel revisions.
>
> Regards,
> Mauro
>
> >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > drivers/media/platform/vsp1/vsp1_drm.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/media/platform/vsp1/vsp1_drm.c
> > > b/drivers/media/platform/vsp1/vsp1_drm.c index 095dc48aa25a..cb6b60843400
> > > 100644
> > > --- a/drivers/media/platform/vsp1/vsp1_drm.c
> > > +++ b/drivers/media/platform/vsp1/vsp1_drm.c
> > > @@ -185,7 +185,7 @@ static int vsp1_du_pipeline_setup_brx(struct vsp1_device
> > > *vsp1, brx = &vsp1->brs->entity;
> > >
> > > /* Switch BRx if needed. */
> > > - if (brx != pipe->brx) {
> > > + if (brx != pipe->brx || !pipe->brx) {
> > > struct vsp1_entity *released_brx = NULL;
> > >
> > > /* Release our BRx if we have one. */
> >
>
>
>
> Thanks,
> Mauro
Thanks,
Mauro
prev parent reply other threads:[~2018-08-08 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 12:13 [PATCH] media: vsp1: cleanup a false positive warning Mauro Carvalho Chehab
2018-05-04 14:37 ` Geert Uytterhoeven
2018-05-04 15:32 ` Mauro Carvalho Chehab
2018-05-07 14:05 ` Laurent Pinchart
2018-05-07 15:21 ` Mauro Carvalho Chehab
2018-08-08 13:58 ` Mauro Carvalho Chehab [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=20180808105820.67469806@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).