From: Lourdes Pedrajas <lu@pplo.net>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Trying to use Coccinelle
Date: Fri, 13 Mar 2020 10:40:46 +0100 [thread overview]
Message-ID: <20200313094046.GB3844@supernova> (raw)
In-Reply-To: <20200312002348.06821daa@elisabeth>
On Thu, Mar 12, 2020 at 12:23:48AM +0100, Stefano Brivio wrote:
> On Wed, 11 Mar 2020 19:11:34 +0100
> Lourdes Pedrajas <lu@pplo.net> wrote:
>
> > Hello, I compiled Coccinelle successfully but maybe I am not getting it.
> > In order to try it in drivers/staging I ran e.g.:
> >
> > make coccicheck MODE=patch M=drivers/staging/android/
> >
> > and then got:
> >
> > coccicheck failed
> > make: *** [coccicheck] Error 255
> > Makefile:1740: recipe for target 'coccicheck' failed.
> >
> > Also tried some modifications of the command, read this documentation:
> > https://www.kernel.org/doc/html/latest/dev-tools/coccinelle.html and searched
> > how to use it, but nothing did help.
> >
> > Only when I ran make coccicheck MODE=patch over entire sources it
> > produces some good results, but eventually I got
> >
> > coccicheck failed
> > Makefile:1740: recipe for target 'coccicheck' failed
> > make: *** [coccicheck] Error 255
>
> Can you share a bit more output? What comes before that?
>
> --
> Stefano
>
Hi Stefano,
Indeed, this is all the output: (this command is run in the sources root
directory)
make coccicheck MODE=patch J=8 M=drivers/staging/android/
Please check for false positives in the output before submitting a patch.
When using "patch" mode, carefully review the patch before submitting it.
coccicheck failed
Makefile:1740: recipe for target 'coccicheck' failed
make: *** [coccicheck] Error 255
Maybe I should try to use the distribution package instead? The
compilation wasn't smooth either, it gave me some autoconf errors I eventually
solved. However, if I run this command to compile all sources, it works, prints
some patches for the drivers/ directory in the standard output, but after a
little (and before descending to drivers/staging/ directory), it gives the same
error (I will skip some output and only copy the last patch it produces):
make coccicheck MODE=patch J=8
Please check for false positives in the output before submitting a patch.
When using "patch" mode, carefully review the patch before submitting it.
... (output skipped - various patches)
diff -u -p a/drivers/s390/crypto/zcrypt_ep11misc.c b/drivers/s390/crypto/zcrypt_ep11misc.c
--- a/drivers/s390/crypto/zcrypt_ep11misc.c
+++ b/drivers/s390/crypto/zcrypt_ep11misc.c
@@ -195,11 +195,10 @@ static inline struct ep11_cprb *alloc_cp
size_t len = sizeof(struct ep11_cprb) + payload_len;
struct ep11_cprb *cprb;
- cprb = kmalloc(len, GFP_KERNEL);
+ cprb = kzalloc(len, GFP_KERNEL);
if (!cprb)
return NULL;
- memset(cprb, 0, len);
cprb->cprb_len = sizeof(struct ep11_cprb);
cprb->cprb_ver_id = 0x04;
memcpy(cprb->func_id, "T4", 2);
coccicheck failed
Makefile:1740: recipe for target 'coccicheck' failed
make: *** [coccicheck] Error 255
Maybe I am not using the command properly? I searched how to do it and
didn't get it, sorry :(
Thank you for your help!
next prev parent reply other threads:[~2020-03-13 9:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 18:11 Trying to use Coccinelle Lourdes Pedrajas
2020-03-11 23:23 ` [Outreachy kernel] " Stefano Brivio
2020-03-13 9:40 ` Lourdes Pedrajas [this message]
2020-03-16 14:08 ` Stefano Brivio
2020-03-16 14:27 ` Julia Lawall
2020-03-16 14:36 ` Stefano Brivio
2020-03-16 14:44 ` Julia Lawall
2020-03-16 15:23 ` Stefano Brivio
2020-03-16 15:32 ` Julia Lawall
2020-03-16 15:44 ` Stefano Brivio
2020-03-19 20:15 ` Lourdes Pedrajas
2020-03-19 20:25 ` Julia Lawall
2020-03-19 20:43 ` Stefano Brivio
2020-03-19 21:30 ` Lourdes Pedrajas
2020-03-19 21:38 ` Julia Lawall
2020-03-19 21:47 ` Lourdes Pedrajas
2020-03-19 21:50 ` Julia Lawall
2020-03-19 22:06 ` Lourdes Pedrajas
2020-03-23 0:00 ` Stefano Brivio
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=20200313094046.GB3844@supernova \
--to=lu@pplo.net \
--cc=outreachy-kernel@googlegroups.com \
--cc=sbrivio@redhat.com \
/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.