All of lore.kernel.org
 help / color / mirror / Atom feed
From: der.herr@hofr.at (Nicholas Mc Guire)
To: cocci@systeme.lip6.fr
Subject: [Cocci] How to use coccinelle as a kind of grep -l ?
Date: Mon, 1 Dec 2014 11:37:06 +0100	[thread overview]
Message-ID: <20141201103706.GA27923@opentech.at> (raw)
In-Reply-To: <547C4194.5040002@inria.fr>

On Mon, 01 Dec 2014, Francois Berenger wrote:

> On 12/01/2014 11:12 AM, Francois Berenger wrote:
>> Hello,
>>
>
> Instead of applying ...
>
>> Inside of applying any patch, I need to use coccinelle
>> in order to detect certain C files that match a given pattern
>> in a source code tree.
>>
>> Is it possible to use coccinelle for that, how?
>>
>
here is a simple (hopefuly correct) example of a scanner - that will look
for inbalanced use of spinlocks and bh disable/enable - it reports one 
line per file that matches giving the name and line-numbers of the 
potentially inballanced calls. 


@r1@                                                                            
identifier f;
expression E;
position p1,p2,p3;
@@
f(...) {
<...
(
spin_lock_bh(E)@p1;
...
spin_unlock(E)@p2;
...
local_bh_enable()@p3;
|
local_bh_disable()@p2;
...
spin_lock(E)@p3;
...
spin_unlock_bh(E)@p1;
)
...>
}

@script:python@
p1 << r1.p1;
p2 << r1.p2;
p3 << r1.p3;
@@
print "file:%s at lines %s %s %s" % (p1[0].file,p1[0].line, p2[0].line, p3[0].line)


put this in a file called scan.cocci and running with the below command 
gives me:

hofrat at debian:/usr/src/linux-next$ spatch --cocci-file /tmp/scan.cocci --dir net/core/
HANDLING: net/core/datagram.c
HANDLING: net/core/netpoll.c
...
HANDLING: net/core/sock.c
file:net/core/sock.c at lines 2396 2406 2411
file:net/core/sock.c@lines 2346 2350 2355
...


thx!
hofrat

  reply	other threads:[~2014-12-01 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 10:12 [Cocci] How to use coccinelle as a kind of grep -l ? Francois Berenger
2014-12-01 10:23 ` Francois Berenger
2014-12-01 10:37   ` Nicholas Mc Guire [this message]
2014-12-01 10:24 ` Julia Lawall

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=20141201103706.GA27923@opentech.at \
    --to=der.herr@hofr.at \
    --cc=cocci@systeme.lip6.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.