public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
	Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: fs/ocfs2/suballoc.c:2430:2-8: preceding lock on line 2413
Date: Fri, 14 Aug 2020 21:52:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2008142148180.2441@hadrien> (raw)
In-Reply-To: <87364pkock.fsf@nanos.tec.linutronix.de>



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?

thanks,
julia

  reply	other threads:[~2020-08-14 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  6:11 fs/ocfs2/suballoc.c:2430:2-8: preceding lock on line 2413 kernel test robot
2020-08-14 13:32 ` Thomas Gleixner
2020-08-14 19:00   ` Julia Lawall
2020-08-14 19:40     ` Thomas Gleixner
2020-08-14 19:52       ` Julia Lawall [this message]
2020-08-15 12:52         ` [kbuild-all] " Philip Li

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=alpine.DEB.2.22.394.2008142148180.2441@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=jack@suse.cz \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nicolas.palix@imag.fr \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    /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