From: Aditya <yashsri421@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] checkpatch: fix false positive for REPEATED_WORD warning
Date: Wed, 21 Oct 2020 14:05:44 +0530 [thread overview]
Message-ID: <e50f6236-e4a2-49e5-c777-358de7b2ffe6@gmail.com> (raw)
In-Reply-To: <CABJPP5CRJTe3wuLwo8HpFX_dygThic6Ci1=L1=6x0p6e+yR32g@mail.gmail.com>
On 21/10/20 1:50 pm, Dwaipayan Ray wrote:
> Hey Aditya and Lukas,
>
>>>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>>>> index 9b9ffd876e8a..181c95691715 100755
>>>> --- a/scripts/checkpatch.pl
>>>> +++ b/scripts/checkpatch.pl
>>>> @@ -3052,7 +3052,9 @@ sub process {
>>>>
>>>> # check for repeated words separated by a single space
>>>> if ($rawline =~ /^\+/ || $in_commit_log) {
>>>> - while ($rawline =~ /\b($word_pattern) (?=($word_pattern))/g) {
>>>> + # avoid repeating hex occurrences like 'ff ff fe 09 ...'
>>>> + while ($rawline !~ /((\s)*[0-9a-z]{2}( )+){4,}/ &&
>
> Pattern is probably wrong. It doesn't recognize word boundaries or
> tabs between words. Example of the first type:
>
> 000 00 ff ff ...
>
> The regex matches "00 00 ff ff" ignoring the first 0.
>
> I think it could be perhaps better with something like:
>
> # check for repeated words separated by a single space
> - if ($rawline =~ /^\+/ || $in_commit_log) {
> + if (($rawline =~ /^\+/ || $in_commit_log) &&
> + $rawline !~ /(?:\b(?:[0-9a-f]{2}\s+){4,})/) {
> pos($rawline) = 1 if (!$in_commit_log);
> while ($rawline =~ /\b($word_pattern)
> (?=($word_pattern))/g) {
>
> Please test it though. I only ran it on a few patterns.
>
> Apart from it, this does fix the problem. But I am quite sceptical about
> matching 4 or more 2 lettered words in a row. There could be counter
> examples but I guess that is very rare. It's not very general, but for
> the moment it does the job.
>
> So I think it's probably good with some changes. Not sure what Joe
> would have in mind though.
>
> Lukas, I think with the changes in place, it is ready to go for discussion.
>
> Thanks,
> Dwaipayan.
>
Thanks Dwaipayan. You're correct.
I'll use \b for checking the word boundaries and regenerate the
reports. I used 4 as the minimum as there were some occurrences with 4
hex words, For eg,
WARNING:REPEATED_WORD: Possible repeated word: 'ff'
#15:
d68: 61 29 ff ff ori r9,r9,65535
for the commit 332ce969b763 ("powerpc/8xx: Reduce time spent in
allow_user_access() and friends")
In addition to your changes, I also plan to modify regex with [0-9a-f]
(instead of a-z).
I'll apply all the changes and send the report, along with the removed
warnings again.
Thanks
Aditya
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-10-21 8:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 5:00 [Linux-kernel-mentees] [PATCH] checkpatch: fix false positive for REPEATED_WORD warning Aditya Srivastava
2020-10-21 5:15 ` Aditya
2020-10-21 6:12 ` Lukas Bulwahn
2020-10-21 8:20 ` Dwaipayan Ray
2020-10-21 8:35 ` Aditya [this message]
2020-10-21 8:52 ` Lukas Bulwahn
2020-10-21 12:09 ` Aditya
2020-10-21 12:53 ` Aditya
2020-10-21 12:58 ` Lukas Bulwahn
2020-10-21 12:59 ` Dwaipayan Ray
-- strict thread matches above, loose matches on Subject: below --
2020-10-21 14:44 Aditya Srivastava
2020-10-21 14:50 ` Lukas Bulwahn
2020-10-21 15:01 Aditya Srivastava
2020-10-21 15:08 ` Lukas Bulwahn
2020-10-21 15:18 ` Joe Perches
2020-10-21 15:28 ` Joe Perches
2020-10-21 16:50 ` Joe Perches
2020-10-21 16:59 ` Dwaipayan Ray
2020-10-21 17:17 ` Joe Perches
2020-10-21 17:55 ` Aditya
2020-10-21 18:05 ` Joe Perches
2020-10-21 18:25 ` Aditya
2020-10-21 19:12 ` Lukas Bulwahn
2020-10-22 14:21 ` Aditya
2020-10-22 14:35 ` Joe Perches
2020-10-21 19:10 ` Aditya
2020-10-21 19:26 ` Joe Perches
2020-10-21 20:36 ` Joe Perches
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=e50f6236-e4a2-49e5-c777-358de7b2ffe6@gmail.com \
--to=yashsri421@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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