From: Joe Perches <joe@perches.com>
To: Quentin Monnet <quentin@isovalent.com>,
Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: fix CONST_STRUCT when const_structs.checkpatch is missing
Date: Mon, 22 Jun 2020 14:24:47 -0700 [thread overview]
Message-ID: <8a218fa14cc2e1690df32d278c82587c7507a820.camel@perches.com> (raw)
In-Reply-To: <20200622204844.21030-1-quentin@isovalent.com>
On Mon, 2020-06-22 at 21:48 +0100, Quentin Monnet wrote:
> Checkpatch reports warnings when some specific structs are not declared
> as const in the code. The list of structs to consider was initially
> defined in the checkpatch.pl script itself, but it was later moved to an
> external file (scripts/const_structs.checkpatch). This introduced two
> minor issues:
>
> - When file scripts/const_structs.checkpatch is not present (for
> example, if checkpatch is run outside of the kernel directory with the
> "--no-tree" option), a warning is printed to stderr to tell the user
> that "No structs that should be const will be found". This is fair,
> but the warning is printed unconditionally, even if the option
> "--ignore CONST_STRUCT" is passed. In the latter case, we explicitly
> ask checkpatch to skip this check, so no warning should be printed.
>
> - When scripts/const_structs.checkpatch is missing, or even when trying
> to silence the warning by adding an empty file, $const_structs is set
> to "", and the regex used for finding structs that should be const,
> "$line =~ /\bstruct\s+($const_structs)\b(?!\s*\{)/)", matches all
> structs found in the code, thus reporting a number of false positives.
>
> Let's fix the first item by skipping scripts/const_structs.checkpatch
> processing if "CONST_STRUCT" checks are ignored, and the second one by
> skipping the test if $const_structs is an empty string.
>
> Fixes: bf1fa1dae68e ("checkpatch: externalize the structs that should be const")
Probably not worthy of a Fixes: line, as that's
generally used for backporting, but OK by me.
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -781,8 +781,10 @@ sub read_words {
> }
>
> my $const_structs = "";
This might be a tiny bit faster/less cpu using:
my $const_structs;
> -read_words(\$const_structs, $conststructsfile)
> - or warn "No structs that should be const will be found - file '$conststructsfile': $!\n";
> +if (show_type("CONST_STRUCT")) {
> + read_words(\$const_structs, $conststructsfile)
> + or warn "No structs that should be const will be found - file '$conststructsfile': $!\n";
> +}
>
> my $typeOtherTypedefs = "";
> if (length($typedefsfile)) {
> @@ -6660,7 +6662,8 @@ sub process {
>
> # check for various structs that are normally const (ops, kgdb, device_tree)
> # and avoid what seem like struct definitions 'struct foo {'
> - if ($line !~ /\bconst\b/ &&
> + if ($const_structs ne "" &&
instead testing
if (defined($const_structs) &&
> + $line !~ /\bconst\b/ &&
> $line =~ /\bstruct\s+($const_structs)\b(?!\s*\{)/) {
> WARN("CONST_STRUCT",
> "struct $1 should normally be const\n" . $herecurr);
next prev parent reply other threads:[~2020-06-22 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:48 Quentin Monnet
2020-06-22 21:24 ` Joe Perches [this message]
2020-06-23 10:33 ` Quentin Monnet
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=8a218fa14cc2e1690df32d278c82587c7507a820.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin@isovalent.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
all inboxes | Powered by JetHome®