From: Joe Perches <joe@perches.com>
To: Aditya Srivastava <yashsri421@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
lukas.bulwahn@gmail.com, dwaipayanray1@gmail.com
Subject: Re: [PATCH v2] checkpatch: fix false positives in REPEATED_WORD warning
Date: Thu, 22 Oct 2020 09:10:59 -0700 [thread overview]
Message-ID: <4cbbd8d8b6c4d686f71648af8bc970baa4b0ee9b.camel@perches.com> (raw)
In-Reply-To: <20201022145021.28211-1-yashsri421@gmail.com>
On Thu, 2020-10-22 at 20:20 +0530, Aditya Srivastava wrote:
> Presence of hexadecimal address or symbol results in false warning
> message by checkpatch.pl.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -3051,7 +3051,10 @@ sub process {
> }
>
> # check for repeated words separated by a single space
> - if ($rawline =~ /^\+/ || $in_commit_log) {
> +# avoid false positive from list command eg, '-rw-r--r-- 1 root root'
> + if (($rawline =~ /^\+/ || $in_commit_log) &&
> + $rawline !~ /[bcCdDlMnpPs\?-][rwxsStT-]{9}/) {
Alignment and use \b before and after the regex please.
if (($rawline =~ /^\+/ || $in_commit_log) &&
$rawline !~ /\b[bcCdDlMnpPs\?-][rwxsStT-]{9}\b/) {
> @@ -3065,6 +3068,34 @@ sub process {
> next if ($first ne $second);
> next if ($first eq 'long');
>
> + # avoid repeating hex occurrences like 'ff ff fe 09 ...'
> + if ($first =~ /\b[0-9a-f]{2,}/) {
> + # if such sequence occurs more than 4, it is most probably part of some of code
> + next if ((scalar @hex_seq)>4);
> + # for hex occurrences which are less than 4
> + # get first hex word in the line
> + if ($rawline =~ /\b[0-9a-f]{2,} /) {
> + my $post_hex_seq = $';
> +
> + # set suffieciently high default values to avoid ignoring or counting in absence of another
> + my $non_hex_char_pos = 1000;
> + my $special_chars_pos = 500;
> +
> + if ($post_hex_seq =~ /[g-z]+/) {
> + # first non hex character in post_hex_seq
> + $non_hex_char_pos = $-[0];
> + }
> + if($post_hex_seq =~ /[^a-zA-Z0-9]{2,}/) {
> + # first occurrence of 2 or more special chars
> + $special_chars_pos = $-[0];
> + }
What does all this code actually avoid?
next prev parent reply other threads:[~2020-10-22 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 14:50 Aditya Srivastava
2020-10-22 14:58 ` Aditya
2020-10-22 16:10 ` Joe Perches [this message]
2020-10-22 19:14 ` Aditya
2020-10-22 19:33 ` Joe Perches
2020-10-22 21:05 ` Aditya
2020-10-22 22:46 ` Joe Perches
2020-10-23 6:33 ` Aditya
2020-10-23 6:38 ` Aditya
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=4cbbd8d8b6c4d686f71648af8bc970baa4b0ee9b.camel@perches.com \
--to=joe@perches.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=yashsri421@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
all inboxes | Powered by JetHome®