From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>
Cc: Dan Carpenter <error27@gmail.com>,
Julia Lawall <julia.lawall@lip6.fr>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH V2] checkpatch: Check output format style of __func__ uses
Date: Sun, 13 Mar 2016 17:42:59 -0700 [thread overview]
Message-ID: <5db4d45c04c506d23ab5b35527e2a544e86c4c6d.1457915615.git.joe@perches.com> (raw)
In-Reply-To: <83a6236111861645daa6dee9ae7f7aeb03cd7b14.1457896085.git.joe@perches.com>
Loggng messages that emit function names have many different forms.
Perhaps it'd be better for logging consistency and grep ease to
exclusively use "%s:"
As well, function tracing logging uses are generally unnecessary given
the kernel's function tracing (ftrace) capability.
Right now, grep shows these mixtures of forms:
13704 "%s:"
3839 "%s "
2787 "%s()"
Some of these are macros definitions of various styles.
Unfortunately, given the complexity of these macro definition styles,
checkpatch isn't an ideal tool to find these macros.
Maybe a coccinelle script might be better suited to find and fix all
the various types of uses.
Add a --fix option for these logging messages with __func__.
Signed-off-by: Joe Perches <joe@perches.com>
---
v2: Warn on function tracing logging
Add --fix option
scripts/checkpatch.pl | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 75ce6d0..b695f75 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -1415,6 +1415,22 @@ sub raw_line {
return $line;
}
+sub cooked_line {
+ my ($linenr, $cnt) = @_;
+
+ my $offset = $linenr - 1;
+ $cnt++;
+
+ my $line;
+ while ($cnt) {
+ $line = $lines[$offset++];
+ next if (defined($line) && $line =~ /^-/);
+ $cnt--;
+ }
+
+ return $line;
+}
+
sub cat_vet {
my ($vet) = @_;
my ($res, $coded);
@@ -5681,6 +5697,45 @@ sub process {
}
}
+# check how __func__ is formatted, prefer "%s:...', __func__
+ if ($^V && $^V ge 5.10.0 &&
+ defined $stat &&
+ $stat =~ /\b__func__\b/ &&
+ $stat =~ /^\+\s*$logFunctions\s*\(\s*[^"]*$String\s*,\s*__func__\b/m &&
+ (() = $stat =~ /^\+|\n\+/g) == 1 &&
+ (() = $stat =~ /;/g) <= 1) {
+ my $herectx = $here . "\n";
+ my $cooked_linenr = -1;
+ my $cooked_line = "";
+ my $raw_line = "";
+ my $cnt = statement_rawlines($stat);
+ for (my $n = 0; $n < $cnt; $n++) {
+ $herectx .= raw_line($linenr, $n) . "\n";
+ if ($cooked_linenr == -1 && cooked_line($linenr, $n) =~ /$String/) {
+ $cooked_linenr = $linenr + $n;
+ $cooked_line = cooked_line($linenr, $n);
+ $raw_line = raw_line($linenr, $n);
+ }
+ }
+ my $qs = get_quoted_string($cooked_line, $raw_line);
+ if ($qs =~ /^"\s*%s(?:[\s:\-]*|[\s:\-]*\(\s*\)\s*[\s:\-]*)?(?:enter|entering|entered|exit|exiting)?\s*\.*\s*\\n"$/i) {
+ if (WARN("FUNC_STYLE",
+ "Prefer using ftrace to logging function entry/exit\n" . $herectx) &&
+ $cnt == 1 &&
+ $fix) {
+ fix_delete_line($fixlinenr, $rawline);
+ }
+ } elsif ($qs !~ /^"%s:/) {
+ if (WARN("FUNC_STYLE",
+ "Prefer using formatting style '%s:' for __func__\n" . $herectx) &&
+ $fix) {
+ $fixed[$cooked_linenr - 1] =~ s/[:\s]*%s(?:[:\s,\-]*|[\s:\-]*\(\s*\)\s*[\s:\-]*)?//;
+ $fixed[$cooked_linenr - 1] =~ s/"/"%s: /;
+ $fixed[$cooked_linenr - 1] =~ s/"%s: \\n/"%s\\n/;
+ }
+ }
+ }
+
# check for uses of __DATE__, __TIME__, __TIMESTAMP__
while ($line =~ /\b(__(?:DATE|TIME|TIMESTAMP)__)\b/g) {
ERROR("DATE_TIME",
--
2.6.3.368.gf34be46
next prev parent reply other threads:[~2016-03-14 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 19:19 [RFC PATCH] checkpatch: check formatting of __func__ output uses Joe Perches
2016-03-14 0:42 ` Joe Perches [this message]
2016-03-14 5:19 ` [RFC PATCH V2] checkpatch: Check output format style of __func__ uses Julia Lawall
2016-03-14 7:35 ` Joe Perches
2016-03-14 8:29 ` Julia Lawall
2016-03-14 14:07 ` 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=5db4d45c04c506d23ab5b35527e2a544e86c4c6d.1457915615.git.joe@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=error27@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).