From: Joe Perches <joe@perches.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] checkpatch.pl: fix naked sscanf false positives
Date: Sat, 06 Feb 2016 05:26:31 +0000 [thread overview]
Message-ID: <1454736391.3263.19.camel@perches.com> (raw)
In-Reply-To: <20160205082952.GA18361@kwern-VirtualBox>
On Fri, 2016-02-05 at 00:29 -0800, Kevin Wern wrote:
> There is a section of checkpatch.pl that intends to ensure the return
> value of sscanf is always checked. However, in certain cases, like in
> drivers/staging/dgnc/dgnc.mod.c, the symbol for sscanf is used without
> calling the function:
>
> static const struct modversion_info ____versions[]
> __used
> __attribute__((section("__versions"))) = {
> ...
> { 0x20c55ae0, __VMLINUX_SYMBOL_STR(sscanf) },
> ...
> };
>
> This currently results in a warning, which is undesirable. We should
> adjust the script's first regex condition to match *calls* to sscanf,
> not just the symbol itself.
>
> Signed-off-by: Kevin Wern <kevin.m.wern@gmail.com>
> ---
> scripts/checkpatch.pl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 0147c91..199247d 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -5452,7 +5452,7 @@ sub process {
> # check for naked sscanf
> if ($^V && $^V ge 5.10.0 &&
> defined $stat &&
> - $line =~ /\bsscanf\b/ &&
> + $line =~ /\bsscanf\b\s*$balanced_parens/ &&
No, that won't work. That's what the $stat line is for
I suppose it could be /\bsscanf\s*\(/ though
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-06 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 8:29 [PATCH] checkpatch.pl: fix naked sscanf false positives Kevin Wern
2016-02-05 9:46 ` Dan Carpenter
2016-02-06 5:26 ` Joe Perches [this message]
2016-02-06 6:58 ` Kevin Wern
2016-02-06 17:20 ` Joe Perches
2016-02-06 21:24 ` Kevin Wern
2016-02-06 23:08 ` Joe Perches
2016-02-12 5:35 ` Kevin Wern
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=1454736391.3263.19.camel@perches.com \
--to=joe@perches.com \
--cc=kernel-janitors@vger.kernel.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