From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Mrinal Pandey <mrinalmni@gmail.com>, joe@perches.com
Cc: apw@canonical.com, linux-kernel@vger.kernel.org,
lukas.bulwahn@gmail.com, skhan@linuxfoundation.org,
Linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v2] checkpatch: Fix the usage of capture group ( ... )
Date: Thu, 30 Jul 2020 07:58:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2007300746330.13710@felia> (raw)
In-Reply-To: <20200714032352.f476hanaj2dlmiot@mrinalpandey>
On Tue, 14 Jul 2020, Mrinal Pandey wrote:
> The usage of "capture group (...)" in the immediate condition after `&&`
> results in `$1` being uninitialized. This issues a warning "Use of
> uninitialized value $1 in regexp compilation at ./scripts/checkpatch.pl
> line 2638".
>
> I noticed this bug while running checkpatch on the set of commits from
> v5.7 to v5.8-rc1 of the kernel on the commits with a diff content in
> their commit message.
>
> This bug was introduced in the script by commit e518e9a59ec3
> ("checkpatch: emit an error when there's a diff in a changelog"). It has
> been in the script since then.
>
> The author intended to store the match made by capture group in variable
> `$1`. This should have contained the name of the file as `[\w/]+` matched.
> However, this couldn't be accomplished due to usage of capture group and
> `$1` in the same regular expression.
>
> Fix this by placing the capture group in the condition before `&&`.
> Thus, `$1` can be initialized to the text that capture group matches
> thereby setting it to the desired and required value.
>
> Reviewed-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Tested-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Signed-off-by: Mrinal Pandey <mrinalmni@gmail.com>
> ---
> Changes since v1:
> Add Reviewed-by and Tested-by tag
>
Hi Joe,
did you see this quick fix to checkpatch.pl? Can you comment on the
commit and can we get a quick ack on that fix, please?
General question on patches for ./scripts/checkpatch.pl:
How do they travel to Linus?
Do you pick those patches and provide them to Andrew Morton?
Or do you just ack them and we need to send them to Andrew Morton to get
them into mainline?
(get_maintainers tells us to just send those patches to you and Andy.)
Lukas
> scripts/checkpatch.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 4c820607540b..e73e998d582a 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2636,8 +2636,8 @@ sub process {
>
> # Check if the commit log has what seems like a diff which can confuse patch
> if ($in_commit_log && !$commit_log_has_diff &&
> - (($line =~ m@^\s+diff\b.*a/[\w/]+@ &&
> - $line =~ m@^\s+diff\b.*a/([\w/]+)\s+b/$1\b@) ||
> + (($line =~ m@^\s+diff\b.*a/([\w/]+)@ &&
> + $line =~ m@^\s+diff\b.*a/[\w/]+\s+b/$1\b@) ||
> $line =~ m@^\s*(?:\-\-\-\s+a/|\+\+\+\s+b/)@ ||
> $line =~ m/^\s*\@\@ \-\d+,\d+ \+\d+,\d+ \@\@/)) {
> ERROR("DIFF_IN_COMMIT_MSG",
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2020-07-30 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:23 [PATCH v2] checkpatch: Fix the usage of capture group ( ... ) Mrinal Pandey
2020-07-14 5:47 ` Lukas Bulwahn
2020-07-30 5:58 ` Lukas Bulwahn [this message]
2020-07-30 7:31 ` Joe Perches
2020-08-20 4:52 ` Mrinal Pandey
2020-08-21 4:25 ` 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=alpine.DEB.2.21.2007300746330.13710@felia \
--to=lukas.bulwahn@gmail.com \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrinalmni@gmail.com \
--cc=skhan@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).