From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: patches@linaro.org, Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] checkpatch: Don't emit spurious warnings about block comments
Date: Fri, 18 Jan 2019 11:06:45 -0600 [thread overview]
Message-ID: <e0d4eed9-c715-a20e-d3bc-85ab11876cca@redhat.com> (raw)
In-Reply-To: <20190118165050.22270-1-peter.maydell@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
On 1/18/19 10:50 AM, Peter Maydell wrote:
> In checkpatch we attempt to check for and warn about
> block comments which start with /* or /** followed by a
> non-blank. Unfortunately a bug in the regex meant that
> we would incorrectly warn about comments starting with
> "/**" with no following text:
>
> git show 9813dc6ac3954d58ba16b3920556f106f97e1c67|./scripts/checkpatch.pl -
> WARNING: Block comments use a leading /* on a separate line
> #34: FILE: tests/libqtest.h:233:
> +/**
>
> The sequence "/\*\*?" was intended to match either "/*" or "/**",
> but Perl's semantics for '?' allow it to backtrack and try the
> "matches 0 chars" option if the "matches 1 char" choice leads to
> a failure of the rest of the regex to match. Switch to "/\*\*?+"
> which uses what perlre(1) calls the "possessive" quantifier form:
> this means that if it matches the "/**" string it will not later
> backtrack to matching just the "/*" prefix.
>
> The other end of the regex is also wrong: it is attempting
> to check for "/* or /** followed by something that isn't
> just whitespace", but [ \t]*.+[ \t]* will match on pure
> whitespace. This is less significant but means that a line
> with just a comment-starter followed by trailing whitespace
> will generate an incorrect warning about block comment style
> as well as the correct error about trailing whitespace which
> a different checkpatch test emits.
>
Fixes: 8c06fbdf36bf4d4d486116200248730887a4d7d6
> Reported-by: Thomas Huth <thuth@redhat.com>
> Reported-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> # Block comments use /* on a line of its own
> if ($rawline !~ m@^\+.*/\*.*\*/[ \t]*$@ && #inline /*...*/
> - $rawline =~ m@^\+.*/\*\*?[ \t]*.+[ \t]*$@) { # /* or /** non-blank
> + $rawline =~ m@^\+.*/\*\*?+[ \t]*[^ \t]@) { # /* or /** non-blank
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-18 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 16:50 [Qemu-devel] [PATCH v2] checkpatch: Don't emit spurious warnings about block comments Peter Maydell
2019-01-18 17:06 ` Eric Blake [this message]
2019-01-24 14:04 ` Peter Maydell
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=e0d4eed9-c715-a20e-d3bc-85ab11876cca@redhat.com \
--to=eblake@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).