From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>, cocci@systeme.lip6.fr
Subject: Re: [Cocci] coccinelle issues
Date: Sun, 14 Jun 2020 10:00:50 +0200 [thread overview]
Message-ID: <1592121650.2129.11.camel@gmail.com> (raw)
In-Reply-To: <1592121432.2129.9.camel@gmail.com>
On Sun, 2020-06-14 at 09:57 +0200, Mike Galbraith wrote:
> On Sun, 2020-06-14 at 09:42 +0200, Julia Lawall wrote:
> >
> > On Sun, 14 Jun 2020, Mike Galbraith wrote:
> >
> >
> > > I didn't download, rather pulled/built. I didn't have the same issue
> > > you did, but make coccicheck was a bust here until I backed down to
> > > version 1.0.6. Neither HEAD, 1.0.8 or 1.0.7 ran, and following its
> > > MODE=blah suggestion helped not at all.
> >
> > Did you get a segmentation fault?
>
> Nope. Turned out to be a dinky install gotcha. Creating a symlink..
>
> lrwxrwxrwx 1 root root 27 Jun 14 09:40 /usr/local/coccinelle/lib -> /usr/local/coccinelle/lib64
>
> ..seems to have fixed 1.0.8 all up. The very first time I installed, I
> had to create one directory (forget which) by hand as well.
Oh well, not all fixed up, but it does run.
./fs/xfs/xfs_rmap_item.c:56:5-24: atomic_dec_and_test variation before object free at line 57.
./kernel/nsproxy.c:253:11-30: atomic_dec_and_test variation before object free at line 254.
./net/unix/scm.c:80:6-30: atomic_dec_and_test variation before object free at line 81.
coccicheck failed
make: *** [Makefile:1822: coccicheck] Error 2
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-06-14 8:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 4:07 [Cocci] coccinelle issues Randy Dunlap
2020-06-14 4:07 ` Randy Dunlap
2020-06-14 6:23 ` [Cocci] " Mike Galbraith
2020-06-14 7:42 ` Julia Lawall
2020-06-14 7:57 ` Mike Galbraith
2020-06-14 8:00 ` Mike Galbraith [this message]
2020-06-14 8:11 ` Mike Galbraith
2020-06-14 8:32 ` Mike Galbraith
2020-06-14 8:49 ` Julia Lawall
2020-06-14 8:47 ` Julia Lawall
2020-06-14 8:43 ` Julia Lawall
2020-06-14 8:44 ` Mike Galbraith
2020-06-14 8:51 ` Julia Lawall
2020-06-14 12:59 ` Julia Lawall
2020-06-14 18:21 ` Mike Galbraith
2020-06-14 19:37 ` Julia Lawall
2020-06-15 4:16 ` Mike Galbraith
2020-06-17 16:37 ` Randy Dunlap
2020-06-14 7:39 ` Julia Lawall
2020-06-14 7:39 ` Julia Lawall
2020-06-14 14:40 ` Randy Dunlap
2020-06-14 14:40 ` Randy Dunlap
2020-06-14 15:20 ` Julia Lawall
2020-06-14 15:20 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2020-06-14 16:12 Markus Elfring
2020-06-14 16:12 ` Markus Elfring
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=1592121650.2129.11.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@inria.fr \
--cc=rdunlap@infradead.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 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.