From: Kees Cook <keescook@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] checkpatch: Warn about 0-length and 1-element arrays
Date: Fri, 26 May 2023 19:01:02 -0700 [thread overview]
Message-ID: <202305261859.310EB2972A@keescook> (raw)
In-Reply-To: <c65be7a615f5cfa300289a6f251d97286c8d81e9.camel@perches.com>
On Fri, May 26, 2023 at 06:38:27PM -0700, Joe Perches wrote:
> On Fri, 2023-05-26 at 10:39 -0700, Kees Cook wrote:
> > Fake flexible arrays have been deprecated since last millennium. Proper
> > C99 flexible arrays must be used throughout the kernel so
> > CONFIG_FORTIFY_SOURCE and CONFIG_UBSAN_BOUNDS can provide proper array
> > bounds checking.
> []
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > []
> > @@ -7430,6 +7430,21 @@ sub process {
> > }
> > }
> >
> > +# check for array definition/declarations that should use flexible arrays instead
> > + if ($sline =~ /^[\+ ]\s*}\s*;\s*$/ &&
> > + $prevline =~ /^\+\s*(?:(?:struct|union|enum)\s+$Ident|\}|$Type)\s*$Ident\s*\[\s*(0|1)\s*\]\s*;\s*$/) {
>
> I think this is overly complicated and not necessary
>
> $prevline =~ /^\+\s*$Type\s*$Ident\s*\[\s*(0|1)\s*\]\s*;\s*$/) {
>
> should work no?
>
> ($Type already includes this from @typeList):
> qr{struct\s+$Ident},
> qr{union\s+$Ident},
> qr{enum\s+$Ident},
Hm, I didn't when I originally tried it. I will double-check.
>
> > + if ($1 == '0') {
> > + if (WARN("ZERO_LENGTH_ARRAY",
> > + "Use C99 flexible arrays instead of zero-length arrays - see https://github.com/KSPP/linux/issues/78\n" . $hereprev) &&
> > + $fix) {
> > + $fixed[$fixlinenr - 1] =~ s/\[0\]/[]/g;
>
> And this $fix doesn't work if the line is struct foo bar[ 0 ];
> and the use of /g is odd.
Thanks!
> Because the message is a WARN and not an ERR, please use
> "Prefer/over" and not "Use/instead of"
I will change to ERR, then. We must not use [0]-sized arrays ever.
>
> $fixed[$fixlinenr - 1] =~ s/\[\s*0\s*\]/[]/;
> > + }
> > + } else {
> > + WARN("ONE_ELEMENT_ARRAY",
> > + "Use C99 flexible arrays instead of one-element arrays - see https://github.com/KSPP/linux/issues/79\n" . $hereprev);
> > + }
>
> And this could have a $fix change too
>
> if (WARN("ONE_ELEMENT_ARRAY",
> ...) &&
> $fix) {
> $fixed[$fixlinenr - 1] =~ s/\[\s*1\s*\]/[]/;
Almost never is it possible to only fix the struct when it's a 1-element
array (due to the impact of the size changes that be present in other
code), so I left it out.
I'll send a v3.
-Kees
--
Kees Cook
prev parent reply other threads:[~2023-05-27 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 17:39 [PATCH v2] checkpatch: Warn about 0-length and 1-element arrays Kees Cook
2023-05-27 1:38 ` Joe Perches
2023-05-27 2:01 ` Kees Cook [this message]
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=202305261859.310EB2972A@keescook \
--to=keescook@chromium.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=gustavoars@kernel.org \
--cc=joe@perches.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox