From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dov Murik" <dovmurik@linux.vnet.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v2] checkpatch: Detect '%#' or '%0#' in printf-style format strings
Date: Tue, 22 Sep 2020 12:40:59 +0200 [thread overview]
Message-ID: <262db394-d419-5e6e-2f9b-cbbfa35fe321@redhat.com> (raw)
In-Reply-To: <20200914172623.72955-1-dovmurik@linux.vnet.ibm.com>
On 14/09/20 19:26, Dov Murik wrote:
> According to the coding style document, we should use literal '0x' prefix
> instead of printf's '#' flag (which appears as '%#' or '%0#' in the format
> string). Add a checkpatch rule to enforce that.
>
> Note that checkpatch already had a similar rule for trace-events files.
>
> Example usage:
>
> $ scripts/checkpatch.pl --file chardev/baum.c
> ...
> ERROR: Don't use '#' flag of printf format ('%#') in format strings, use '0x' prefix instead
> #366: FILE: chardev/baum.c:366:
> + DPRINTF("Broken packet %#2x, tossing\n", req); \
> ...
> ERROR: Don't use '#' flag of printf format ('%#') in format strings, use '0x' prefix instead
> #472: FILE: chardev/baum.c:472:
> + DPRINTF("unrecognized request %0#2x\n", req);
> ...
>
> Signed-off-by: Dov Murik <dovmurik@linux.vnet.ibm.com>
> ---
>
> Since v1:
> - consolidate format string checks to avoid code duplication
>
> ---
> scripts/checkpatch.pl | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index bd3faa154c..f8dac953b2 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2880,14 +2880,20 @@ sub process {
> $herecurr);
> }
>
> -# check for %L{u,d,i} in strings
> +# format strings checks
> my $string;
> while ($line =~ /(?:^|")([X\t]*)(?:"|$)/g) {
> $string = substr($rawline, $-[1], $+[1] - $-[1]);
> $string =~ s/%%/__/g;
> + # check for %L{u,d,i} in strings
> if ($string =~ /(?<!%)%L[udi]/) {
> ERROR("\%Ld/%Lu are not-standard C, use %lld/%llu\n" . $herecurr);
> - last;
> + }
> + # check for %# or %0# in printf-style format strings
> + if ($string =~ /(?<!%)%0?#/) {
> + ERROR("Don't use '#' flag of printf format " .
> + "('%#') in format strings, use '0x' " .
> + "prefix instead\n" . $herecurr);
> }
> }
>
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-09-22 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 17:26 [PATCH v2] checkpatch: Detect '%#' or '%0#' in printf-style format strings Dov Murik
2020-09-14 17:49 ` Philippe Mathieu-Daudé
2020-09-22 10:40 ` Paolo Bonzini [this message]
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=262db394-d419-5e6e-2f9b-cbbfa35fe321@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=dovmurik@linux.vnet.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).