[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200815125243.GA21882@intel.com>
Date: Sat, 15 Aug 2020 20:52:43 +0800
From: Philip Li <philip.li@...el.com>
To: Julia Lawall <julia.lawall@...ia.fr>
Cc: Thomas Gleixner <tglx@...utronix.de>,
kernel test robot <lkp@...el.com>, kbuild-all@...ts.01.org,
linux-kernel@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
Jan Kara <jack@...e.cz>, Nicolas Palix <nicolas.palix@...g.fr>
Subject: Re: [kbuild-all] Re: fs/ocfs2/suballoc.c:2430:2-8: preceding lock on
line 2413
On Fri, Aug 14, 2020 at 09:52:13PM +0200, Julia Lawall wrote:
>
>
> On Fri, 14 Aug 2020, Thomas Gleixner wrote:
>
> > Julia,
> >
> > On Fri, Aug 14 2020 at 21:00, Julia Lawall wrote:
> > > On Fri, 14 Aug 2020, Thomas Gleixner wrote:
> > >> That's clearly a false positive. Is there anything what can be done to
> > >> help that cocci script here?
> > >
> > > I have a better version that needs to get pushed.
> > >
> > > But normally these pass through me. Did you get it directly from kbuild?
> >
> > Yes, because I touched the affected lines last :)
>
> Actually, that's not the point. Normally, I get all the reports on this
> case, and then I forward them if they look ok. If I forwarded something
> incorrect, then sorry about that. If the policy has changed for this rule
> to be sending the reports out directlty to the recipients, then I think it
> should be changed back. There are a lot of real bugs with lock usage, but
> there are alot of false positives too. Specifically, the rule looks for
> the case with identical if tests, but only when the branches are identical
> too.
>
> Kbuild people, can this be adjusted? Or have I misunderstood the
> situation?
Hi Julia and Thomas, pls allow us to check this further, usually all cocci
reports will be sent to kbuild@...org for Julia to check. But there maybe
something wrong with this report. We will check the detail in next week as
we have server maintainance during the weekend.
>
> thanks,
> julia
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@...ts.01.org
> To unsubscribe send an email to kbuild-all-leave@...ts.01.org
Powered by blists - more mailing lists