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, 01 May 2013 10:32:40 +0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1305011821230.1968@hadrien> (raw)
In-Reply-To: <20130428190457.Horde.NTwcWjfi51YkygsVUIuvrA7@wimap.feld.cvut.cz>

This has quite a lot of false positives.  For example in
drivers/firewire/nosy.c
at the return 0 just above the label fail_free_irq in the function
add_card.  Return 0 usually indicates success, and the allocated data is
usually saved somwhere before the success exit.  In nosy.c, the allocated
data is stored in a field of the lynx structure, and the lynx structure is
then stored in card_list, via a call to list_add_tail.

Maybe it would be sufficient not to mark a return with p2 when the return
does return 0.  You would thus have:

(
if (id = NULL) { ... }
|
return 0;
|
*return@p2 ...;
)

You might want to limit id to be a "local idexpression" instead of an
arbitrary expression.  If there is x->y = fn(...), x may be a parameter,
or may be a variable that is stored or freed in some other way, hiding the
call to pci_free_consistent.

Also, you don't need the <... ...> around the rule.

There is also a typo in your first keyword.

Anyway, you can make those changes and look at the result, and see what
the rate of false positives seems to be.  It would be good to put a
confidence level in your semantic patch as well.  You can see examples
in the Linux coccinelle directory.

julia

On Tue, 30 Apr 2013, strnape1@fel.cvut.cz wrote:

> Created coccinelle script for reporting missing pci_free_consistent() calls.
>
> Signed-off-by: Petr Strnad <strnape1@fel.cvut.cz>
> ---
> diff --git a/scripts/coccinelle/free/pci_free_consistent.cocci
> b/scripts/coccinelle/free/pci_free_consistent.cocci
> new file mode 100644
> index 0000000..1196485
> --- /dev/null
> +++ b/scripts/coccinelle/free/pci_free_consistent.cocci
> @@ -0,0 +1,32 @@
> +/// Find missing pci_free_consistent for every pci_alloc_consistent.
> +///
> +// Copyright: (C) 2013 Petr Strnad.  GPLv2.
> +// URL: http://coccinelle.lip6.fr/
> +// Keywords: pci_free_consisten, pci_alloc_consistent
> +// Options: --no-includes --include-headers
> +
> +virtual report
> +
> +@search@
> +expression id,x,y,z;
> +position p1,p2;
> +@@
> +
> +<...
> +id = pci_alloc_consistent@p1(x,y,z)
> +... when != pci_free_consistent(x,y,id,z)
> +    when forall
> +(
> +if (id = NULL) { ... }
> +|
> +*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)
>
> --
> 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-01 10:32 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 [this message]
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
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.1305011821230.1968@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