public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scripts: Coccinelle script for pci_free_consistent()
Date: Wed, 08 May 2013 15:52:09 +0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1305081751320.2025@hadrien> (raw)
In-Reply-To: <20130428190457.Horde.NTwcWjfi51YkygsVUIuvrA7@wimap.feld.cvut.cz>

On Wed, 8 May 2013, strnape1@fel.cvut.cz wrote:

> Alright, so should I make a patch from it?

Could you check that it does what you expect?  If everything is OK, then
you can make a patch.

thanks,
julia

> Quoting Julia Lawall <julia.lawall@lip6.fr>:
>
> > Here is a proposal.  Some features:
> >
> > * It assumes that the result of pci_alloc_consistent is null tested, and
> > doesn't report any problems before that.
> >
> > * It uses exists rather than forall, to find a bug when there is a problem
> > on just one execution path.
> >
> > * It gives no warning if the return value is stored elsewhere or is freed
> > under some kinds of if.
> >
> > * It recognizes 1 as a success value.
> >
> > On linux-next, this gives 10 reports.  At least half of them are false
> > positives, mostly due to interprocedural effects, which this rule does not
> > at all take into account.
> >
> > julia
> >
> > /// Find missing pci_free_consistent for every pci_alloc_consistent.
> > ///
> > // Confidence: Moderate
> > // Copyright: (C) 2013 Petr Strnad.  GPLv2.
> > // URL: http://coccinelle.lip6.fr/
> > // Keywords: pci_free_consistent, pci_alloc_consistent
> > // Options: --no-includes --include-headers
> >
> > virtual report
> > virtual org
> >
> > @search@
> > local idexpression id;
> > expression x,y,z,e;
> > position p1,p2;
> > type T;
> > @@
> >
> > id = pci_alloc_consistent@p1(x,y,&z)
> > ... when != e = id
> > if (id = NULL || ...) { ... return ...; }
> > ... when != pci_free_consistent(x,y,id,z)
> >    when != if (id) { ... pci_free_consistent(x,y,id,z) ... }
> >    when != if (y) { ... pci_free_consistent(x,y,id,z) ... }
> >    when != e = (T)id
> >    when exists
> > (
> > return 0;
> > |
> > return 1;
> > |
> > return id;
> > |
> > return@p2 ...;
> > )
> >
> > @script:python depends on report@
> > p1 << search.p1;
> > p2 << search.p2;
> > @@
> >
> > msg = "ERROR: missing pci_free_consistent; pci_alloc_consistent on line %s
> > and return without freeing on line %s" % (p1[0].line,p2[0].line)
> > coccilib.report.print_report(p2[0],msg)
> >
> > @script:python depends on org@
> > p1 << search.p1;
> > p2 << search.p2;
> > @@
> >
> > msg = "ERROR: missing pci_free_consistent; pci_alloc_consistent on line %s
> > and return without freeing on line %s" % (p1[0].line,p2[0].line)
> > cocci.print_main(msg,p1)
> > cocci.print_secs("",p2)
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-05-08 15:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 17:04 [PATCH] scripts: Coccinelle script for pci_free_consistent() strnape1
2013-04-28 23:05 ` Julia Lawall
2013-04-29 21:06 ` strnape1
2013-04-29 23:35 ` Julia Lawall
2013-04-30  7:58 ` strnape1
2013-05-01 10:32 ` Julia Lawall
2013-05-02  0:28 ` strnape1
2013-05-02  0:57 ` Julia Lawall
2013-05-02 15:12 ` strnape1
2013-05-06 20:57 ` Nicolas Palix
2013-05-06 21:20 ` strnape1
2013-05-07  6:55 ` Dan Carpenter
2013-05-07  6:56 ` Julia Lawall
2013-05-08 12:20 ` strnape1
2013-05-08 14:49 ` Julia Lawall
2013-05-08 15:46 ` strnape1
2013-05-08 15:52 ` Julia Lawall [this message]
2013-05-08 16:28 ` strnape1
2013-05-08 21:03 ` strnape1
2013-06-14 13:25   ` Michal Marek
2013-06-25 13:03   ` Nicolas Palix
2013-07-03 13:55     ` Michal Marek

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.02.1305081751320.2025@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=kernel-janitors@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