From: Alejandro Colomar <alx@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Markus Elfring <Markus.Elfring@web.de>,
cocci@inria.fr, Nicolas Palix <nicolas.palix@imag.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, Kees Cook <kees@kernel.org>
Subject: Re: [cocci] [PATCH] scripts/coccinelle: Add script for using ARRAY_END()
Date: Mon, 9 Mar 2026 13:27:35 +0100 [thread overview]
Message-ID: <aa677-Ag_KU8QHjh@devuan> (raw)
In-Reply-To: <f950c541-1c21-7d5-b7d7-1a14bb6e8a4@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Hi Julia,
On 2026-03-09T13:21:23+0100, Julia Lawall wrote:
[...]
> > > > +// Confidence: ???
> > >
> > > I hope that a more reasonable value can be determined for this information.
> >
> > I don't know how the scale works. I know the script has a few false
> > negatives, and AFAIK there are no false positives. To what level of
> > confidence would that belong?
>
> Probably high would be fine. The goal is mostly to indiacte whether the
> results are most likely correct or whether they will require a lot of
> study to know if everything is ok.
Thanks! I've put high with a comment about the false negatives.
[...]
> > > > +// Comments:
> > >
> > > Please omit such an empty field.
> >
> > Ok; thanks!
> >
> > $ grep -rh '^// Comments:' scripts/coccinelle/ | sort | uniq -c
> > 34 // Comments:
> > 2 // Comments: -
> > 1 // Comments: -I ... -all_includes can give more complete results
> > 1 // Comments: Comments on code can be deleted if near code that is removed.
> > 1 // Comments: Some false positives on empty default cases in switch statements.
> > 1 // Comments: requires at least Coccinelle 0.2.4, lex or parse error otherwise
> > $ find scripts/coccinelle/ -type f | wc -l
> > 76
> >
> >
> > It seems around half of the existing scripts have that. You may want to
> > remove those empty comments. I added it because the scripts I looked at
> > do have it.
>
> I don't require taht an empty comments field be removed.
Ok.
> > > …
> > > > +@i@
> > > > +@@
> > > > +
> > > > +#include <linux/kernel.h>
> > >
> > > I doubt that such an SmPL rule would be required.
> >
> > Okay, I'll remove it. Thanks!
>
> I'm lacking context. You maye need this if the file doesn't already have
> it. But it is hard to know if it could be include indirectly...
Hmmm, this macro is defined together with ARRAY_SIZE() in
<linux/array_size.h>. I guess even if a file isn't including that
already (including indirectly), it would do well in including it for
using the macro, so I guess it's okay to remove it here.
The only concern would be files that *can't* possibly include it (maybe
tools/?).
> julia
Cheers,
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-09 12:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 23:20 [cocci] [PATCH v1 0/1] scripts/coccinelle: Add script for using ARRAY_END() Alejandro Colomar
2026-03-05 23:20 ` [cocci] [PATCH v1 1/1] " Alejandro Colomar
2026-03-09 11:17 ` [cocci] [PATCH] " Markus Elfring
2026-03-09 11:59 ` Julia Lawall
2026-03-09 12:16 ` Alejandro Colomar
2026-03-09 12:10 ` Alejandro Colomar
2026-03-09 12:21 ` Julia Lawall
2026-03-09 12:27 ` Alejandro Colomar [this message]
2026-03-09 12:13 ` [cocci] [PATCH v2] " Alejandro Colomar
2026-03-09 14:05 ` Markus Elfring
2026-03-09 14:05 ` Markus Elfring
2026-03-09 14:32 ` [cocci] " Alejandro Colomar
2026-03-09 14:32 ` Alejandro Colomar
2026-03-15 17:17 ` [cocci] " Alejandro Colomar
2026-03-15 17:17 ` Alejandro Colomar
2026-03-15 17:54 ` [cocci] " Julia Lawall
2026-03-15 17:54 ` Julia Lawall
2026-03-15 22:05 ` [cocci] " Alejandro Colomar
2026-03-15 22:05 ` Alejandro Colomar
2026-03-16 7:18 ` [cocci] [v2] " Markus Elfring
2026-03-16 7:18 ` Markus Elfring
2026-03-16 10:39 ` [cocci] " Alejandro Colomar
2026-03-16 10:39 ` Alejandro Colomar
2026-03-16 10:46 ` [cocci] " Markus Elfring
2026-03-16 10:46 ` Markus Elfring
2026-03-15 22:11 ` [cocci] [PATCH v3] " Alejandro Colomar
2026-03-15 22:12 ` Alejandro Colomar
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=aa677-Ag_KU8QHjh@devuan \
--to=alx@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.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.