From: joern@purestorage.com (Jörn Engel)
To: cocci@systeme.lip6.fr
Subject: [Cocci] coccinelle problems with kernel code
Date: Tue, 8 Sep 2015 14:45:36 -0700 [thread overview]
Message-ID: <20150908214536.GC27133@Sligo.logfs.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1509082316550.2050@localhost6.localdomain6>
On Tue, Sep 08, 2015 at 11:17:58PM +0200, Julia Lawall wrote:
> On Tue, 8 Sep 2015, J?rn Engel wrote:
>
> > Tried to use coccinelle on the linux kernel for the first time. It
> > seems to get things mostly right, but not quite. Here is the semantic
> > patch:
> >
> > @@ expression E; @@
> > -down_read(&E->mmap_sem)
> > +mm_read_lock(E)
> > @@ expression E; @@
> > -down_read_trylock(&E->mmap_sem)
> > +mm_read_trylock(E)
> > @@ expression E; @@
> > -up_read(&E->mmap_sem)
> > +mm_read_unlock(E)
> > @@ expression E; @@
> > -down_write(&E->mmap_sem)
> > +mm_write_lock(E)
> > @@ expression E; @@
> > -down_write_trylock(&E->mmap_sem)
> > +mm_write_trylock(E)
> > @@ expression E; @@
> > -up_write(&E->mmap_sem)
> > +mm_write_unlock(E)
>
> So this all went OK?
Mostly. There are still a few troublemakers remaining. But few enough
that I don't mind handling them manually.
Automatic changes:
140 files changed, 581 insertions(+), 581 deletions(-)
Troublemakers:
arch/mips/mm/fault.c (5 lines)
arch/um/include/asm/mmu_context.h (2 lines)
include/linux/huge_mm.h (1 line)
Commandline:
spatch --sp-file mmap_sem.cocci --dir . --macro-file coccinelle.h
If I explicitly pass the two headerfiles as parameters, they get handled
as well. Maybe a bug in the recursive directory walk?
arch/mips/mm/fault.c seems to have a problem with one of the
conditionals. I could reduce things to the following testcase:
void foo(unsigned long address)
{
down_read(&mm->mmap_sem);
vma = find_vma(current->mm, address);
if (!vma)
goto bad_area;
if (vma->vm_start <= address)
goto good_area;
if (!(vma->vm_flags & VM_GROWSDOWN))
goto bad_area;
if (expand_stack(vma, address))
goto bad_area;
bad_area:
up_read(&mm->mmap_sem);
}
Remove the "!(vma->vm_flags & VM_GROWSDOWN)" condition and it works.
Leave the condition and spatch fails silently.
> > I run into problems whenever handling system calls. Looks like the
> > SYSCALL_DEFINE5() macro and friends are causing problems. Here is my
> > attempt to handle things.
> >
> > #define SYSCALL_DEFINE1(func, t1, a1) \
> > asmlinkage unsigned long func(t1 a1)
> > #define SYSCALL_DEFINE2(func, t1, a1, t2, a2) \
> > asmlinkage unsigned long func(t1 a1, t2 a2)
> > #define SYSCALL_DEFINE3(func, t1, a1, t2, a2, t3, a3) \
> > asmlinkage unsigned long func(t1 a1, t2 a2, t3 a3)
> > #define SYSCALL_DEFINE4(func, t1, a1, t2, a2, t3, a3, t4, a4) \
> > asmlinkage unsigned long func(t1 a1, t2 a2, t3 a3, t4 a4)
> > #define SYSCALL_DEFINE5(func, t1, a1, t2, a2, t3, a3, t4, a4, t5, a5) \
> > asmlinkage unsigned long func(t1 a1, t2 a2, t3 a3, t4 a4, t5 a5)
> > #define SYSCALL_DEFINE6(func, t1, a1, t2, a2, t3, a3, t4, a4, t5, a5, t6, a6) \
> > asmlinkage unsigned long func(t1 a1, t2 a2, t3 a3, t4 a4, t5 a5, t6 a6)
> >
> > Should that be included into standard.h?
>
> If it works, I could certainly add it.
It works.
And tracking down failures in coccinelle is definitely more fun than
making 581 manual changes without messing things up. Thank you!
J?rn
--
Homo Sapiens is a goal, not a description.
-- unknown
next prev parent reply other threads:[~2015-09-08 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 18:07 [Cocci] coccinelle problems with kernel code Jörn Engel
2015-09-08 21:17 ` Julia Lawall
2015-09-08 21:45 ` Jörn Engel [this message]
2015-09-09 5:24 ` Julia Lawall
2015-09-09 5:57 ` Jörn Engel
2015-09-09 8:22 ` SF Markus Elfring
2015-09-09 10:08 ` Julia Lawall
2015-09-09 16:40 ` Jörn Engel
2015-09-09 17:50 ` 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=20150908214536.GC27133@Sligo.logfs.org \
--to=joern@purestorage.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox