[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <685e8554eed17eebc731d62336ef30eb44bd14f7.camel@perches.com>
Date: Thu, 30 May 2019 17:54:57 -0700
From: Joe Perches <joe@...ches.com>
To: Matteo Croce <mcroce@...hat.com>, linux-kernel@...r.kernel.org,
Andy Whitcroft <apw@...onical.com>
Cc: Kees Cook <keescook@...omium.org>,
Aaron Tomlin <atomlin@...hat.com>,
Matthew Wilcox <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] checkpatch.pl: Warn on duplicate sysctl local variable
On Fri, 2019-05-31 at 01:51 +0200, Matteo Croce wrote:
> Commit 6a33853c5773 ("proc/sysctl: add shared variables for range check")
> adds some shared const variables to be used instead of a local copy in
> each source file.
> Warn when a chunk duplicates one of these values in a ctl_table struct:
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -6639,6 +6639,13 @@ sub process {
> "unknown module license " . $extracted_string . "\n" . $herecurr);
> }
> }
> +
> +# check for sysctl duplicate constants
> + if ($line =~ /\.extra[12]\s*=\s*&(zero|one|int_max|max_int)\b/) {
> + my $extracted_string = get_quoted_string($line, $rawline);
> + WARN("DUPLICATED_SYSCTL_CONST",
> + "duplicated sysctl range checking value '$1', consider using the shared one in include/linux/sysctl.h" . $extracted_string . "\n" . $herecurr);
> + }
why is $extracted_string used here?
Powered by blists - more mailing lists