From: Joe Perches <joe@perches.com>
To: william.c.roberts@intel.com, linux-kernel@vger.kernel.org,
apw@canonical.com, Andew Morton <akpm@linux-foundation.org>
Cc: keescook@chromium.org, kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH] checkpatch: add warning on %pk instead of %pK usage
Date: Fri, 10 Feb 2017 12:12:29 -0800 [thread overview]
Message-ID: <1486757549.2192.20.camel@perches.com> (raw)
In-Reply-To: <1486755469-21573-1-git-send-email-william.c.roberts@intel.com>
On Fri, 2017-02-10 at 11:37 -0800, william.c.roberts@intel.com wrote:
> From: William Roberts <william.c.roberts@intel.com>
>
> Sample output:
> WARNING: %pk is close to %pK, did you mean %pK?.
> \#20: FILE: drivers/char/applicom.c:230:
> + printk(KERN_INFO "Could not allocate IRQ %d for PCI Applicom device. %pk\n", dev->irq, pci_get_class);
There isn't a single instance of this in the kernel tree.
Maybe if this is really useful, then all the %p<foo> extensions
should be enumerated and all unknown uses should have warnings.
Something like:
---
scripts/checkpatch.pl | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index ad5ea5c545b2..8a90b457e8b5 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -5305,6 +5305,15 @@ sub process {
}
}
+# check for vsprintf extension %p<foo> misuses
+ if ($line =~ /\b$logFunctions\s*\(.*$String/) {
+ my $format = get_quoted_string($line, $rawline);
+ if ($format =~ /(\%[\*\d\.]*p(?![\WFfSsBKRraEhMmIiUDdgVCbGN]).)/) {
+ WARN("VSPRINTF_POINTER_EXTENSION",
+ "Invalid vsprintf pointer extension '$1'\n" . $herecurr);
+ }
+ }
+
# check for logging continuations
if ($line =~ /\bprintk\s*\(\s*KERN_CONT\b|\bpr_cont\s*\(/) {
WARN("LOGGING_CONTINUATION",
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: william.c.roberts@intel.com, linux-kernel@vger.kernel.org,
apw@canonical.com, Andew Morton <akpm@linux-foundation.org>
Cc: keescook@chromium.org, kernel-hardening@lists.openwall.com
Subject: Re: [PATCH] checkpatch: add warning on %pk instead of %pK usage
Date: Fri, 10 Feb 2017 12:12:29 -0800 [thread overview]
Message-ID: <1486757549.2192.20.camel@perches.com> (raw)
In-Reply-To: <1486755469-21573-1-git-send-email-william.c.roberts@intel.com>
On Fri, 2017-02-10 at 11:37 -0800, william.c.roberts@intel.com wrote:
> From: William Roberts <william.c.roberts@intel.com>
>
> Sample output:
> WARNING: %pk is close to %pK, did you mean %pK?.
> \#20: FILE: drivers/char/applicom.c:230:
> + printk(KERN_INFO "Could not allocate IRQ %d for PCI Applicom device. %pk\n", dev->irq, pci_get_class);
There isn't a single instance of this in the kernel tree.
Maybe if this is really useful, then all the %p<foo> extensions
should be enumerated and all unknown uses should have warnings.
Something like:
---
scripts/checkpatch.pl | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index ad5ea5c545b2..8a90b457e8b5 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -5305,6 +5305,15 @@ sub process {
}
}
+# check for vsprintf extension %p<foo> misuses
+ if ($line =~ /\b$logFunctions\s*\(.*$String/) {
+ my $format = get_quoted_string($line, $rawline);
+ if ($format =~ /(\%[\*\d\.]*p(?![\WFfSsBKRraEhMmIiUDdgVCbGN]).)/) {
+ WARN("VSPRINTF_POINTER_EXTENSION",
+ "Invalid vsprintf pointer extension '$1'\n" . $herecurr);
+ }
+ }
+
# check for logging continuations
if ($line =~ /\bprintk\s*\(\s*KERN_CONT\b|\bpr_cont\s*\(/) {
WARN("LOGGING_CONTINUATION",
next prev parent reply other threads:[~2017-02-10 20:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 19:37 [kernel-hardening] [PATCH] checkpatch: add warning on %pk instead of %pK usage william.c.roberts
2017-02-10 19:37 ` william.c.roberts
2017-02-10 20:12 ` Joe Perches [this message]
2017-02-10 20:12 ` Joe Perches
2017-02-10 22:14 ` [kernel-hardening] " Roberts, William C
2017-02-10 22:14 ` Roberts, William C
2017-02-10 22:26 ` [kernel-hardening] " Roberts, William C
2017-02-10 22:26 ` Roberts, William C
2017-02-10 22:49 ` [kernel-hardening] " Joe Perches
2017-02-10 22:49 ` Joe Perches
2017-02-10 22:59 ` [kernel-hardening] " Joe Perches
2017-02-10 22:59 ` Joe Perches
2017-02-10 23:31 ` [kernel-hardening] " Roberts, William C
2017-02-10 23:31 ` Roberts, William C
2017-02-10 23:49 ` [kernel-hardening] " Joe Perches
2017-02-10 23:49 ` Joe Perches
2017-02-10 23:54 ` [kernel-hardening] " Roberts, William C
2017-02-10 23:54 ` Roberts, William C
2017-02-11 0:01 ` [kernel-hardening] " Joe Perches
2017-02-11 0:01 ` Joe Perches
2017-02-11 1:32 ` [kernel-hardening] " Roberts, William C
2017-02-11 1:32 ` Roberts, William C
2017-02-11 3:23 ` [kernel-hardening] " Joe Perches
2017-02-11 3:23 ` Joe Perches
2017-02-13 19:46 ` [kernel-hardening] " Roberts, William C
2017-02-13 19:46 ` Roberts, William C
2017-02-13 20:14 ` [kernel-hardening] " Joe Perches
2017-02-13 20:14 ` Joe Perches
[not found] ` <1487016251.6214.6.camel@perches.com>
[not found] ` <476DC76E7D1DF2438D32BFADF679FC562305F62F@ORSMSX103.amr.corp.intel.com>
2017-02-13 22:20 ` [kernel-hardening] " Joe Perches
2017-02-13 22:20 ` Joe Perches
2017-02-15 23:49 ` [kernel-hardening] " Roberts, William C
2017-02-15 23:49 ` Roberts, William C
2017-02-16 0:19 ` [kernel-hardening] " Joe Perches
2017-02-16 0:19 ` Joe Perches
2017-02-27 16:26 ` [kernel-hardening] " Roberts, William C
2017-02-27 16:26 ` Roberts, William C
2017-02-27 20:54 ` [kernel-hardening] [PATCH] checkpatch: Add ability to find bad uses of vsprintf %p<foo> extensions Joe Perches
2017-02-27 20:54 ` Joe Perches
2017-02-27 21:18 ` [kernel-hardening] " Kees Cook
2017-02-28 15:34 ` [kernel-hardening] " Roberts, William C
2017-02-28 15:34 ` Roberts, William C
2017-03-01 0:06 ` [kernel-hardening] " Andrew Morton
2017-03-01 0:06 ` Andrew Morton
2017-03-01 0:11 ` [kernel-hardening] " Kees Cook
2017-03-01 1:14 ` Joe Perches
2017-03-01 0:12 ` Joe Perches
2017-03-01 0:12 ` 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=1486757549.2192.20.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=william.c.roberts@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.