From: Marion & Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Joe Perches <joe@perches.com>, apw@canonical.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] checkpatch: check for missing \n at the end of logging message
Date: Wed, 8 Apr 2020 22:19:17 +0200 [thread overview]
Message-ID: <48f32229-068d-cc62-b6df-03cdc11b99a4@wanadoo.fr> (raw)
In-Reply-To: <437746b14735ecef311720ad41d5b237209e9674.camel@perches.com>
Le 08/04/2020 à 02:33, Joe Perches a écrit :
> On Tue, 2020-04-07 at 22:49 +0200, Christophe JAILLET wrote:
>> Strings logged with pr_xxx and dev_xxx often lack a trailing '\n'.
>> Introduce new tests to try to catch them early.
>>
>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>> ---
>> This is more a PoC for now.
>>
>> Regex could be improved, merged, ...
>> We could also check for surrounding pr_cont...
>>
>> This patch is based on idea from [1]. coccinelle spots too many places
>> where \n are missing (~ 2800 with the heuristic I've used).
>> Fixing them would be painful.
>> I instead propose to teach checkpatch.pl about it to try to spot cases
>> early and avoid introducing new cases.
>>
>> [1]: https://marc.info/?l=kernel-janitors&m=158619533629657&w=4
>> ---
>> scripts/checkpatch.pl | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index c392ab8ea12e..792804bd6ad9 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -5676,6 +5676,16 @@ sub process {
>> }
>> }
>>
>> +# check for missing \n at the end of logging function
>> + if ($line =~ /\bpr_(emerg|alert|crit|err|warning|warn|notice|info|debug|dbg)\s*\("([^"]*(?<!\\n))"/) {
>> + WARN("MISSING NL",
>> + "Possible missing '\\n' at the end of a log message\n" . $hereprev);
>> + }
>> + if ($line =~ /\bdev_(emerg|alert|crit|err|warning|warn|notice|info|debug|dbg)\s*\([^,]*,\s*"([^"]*(?<!\\n))"/) {
>> + WARN("MISSING NL",
>> + "Possible missing '\\n' at the end of a log message\n" . $hereprev);
>> + }
> This can't work as string is masked to "XXX"
Ok. I wasn't aware of that.
I tested the regex with regex101.org and only tested with patches that
trigger the checkpatch.pl test, and it worked fine for me.
I didn't test with string with trailing \n, that should NOT trigger the
test. I should have! :(
> This is probably better using $stat and checking if a "XX" format
> string exists as 1st or 2nd arg and adding an extraction
> from the $rawline equivalent and checking that.
>
> Also this test should probably using $logFunctions and check
> if the initial block is one of the known functions that
> use a newline termination (pr_|dev_|netdev_|wiphy_)
Agreed but your perl and regex is much more fluent than mine. ;-)
CJ
next prev parent reply other threads:[~2020-04-08 20:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 20:49 [PATCH] checkpatch: check for missing \n at the end of logging message Christophe JAILLET
2020-04-08 0:33 ` Joe Perches
2020-04-08 20:19 ` Marion & Christophe JAILLET [this message]
2020-04-08 2:14 ` Joe Perches
2020-04-08 20:23 ` Marion & Christophe JAILLET
2020-04-09 3:10 ` Joe Perches
2020-04-09 7:24 ` Christophe JAILLET
2020-04-09 7:24 ` Christophe JAILLET
2020-04-09 15:29 ` Joe Perches
2020-04-09 17:34 ` Christophe JAILLET
2020-04-09 17:34 ` Christophe JAILLET
2020-04-09 17:50 ` Joe Perches
2020-04-09 18:52 ` Christophe JAILLET
2020-04-09 18:52 ` Christophe JAILLET
2020-04-09 21:40 ` Joe Perches
2020-04-09 10:40 ` Dan Carpenter
2020-04-10 17:35 ` Christophe JAILLET
2020-04-10 19:46 ` Joe Perches
2020-04-10 19:53 ` Joe Perches
2020-04-11 6:48 ` Christophe JAILLET
2020-04-11 6:48 ` Christophe JAILLET
2020-04-11 10:10 ` Andy? checkpatch $stat question (was: Re: [PATCH] checkpatch: check for missing \n at the end of logging message) Joe Perches
2020-04-11 7:12 ` [PATCH] checkpatch: check for missing \n at the end of logging message Christophe JAILLET
2020-04-11 7:12 ` Christophe JAILLET
2020-04-11 7:13 ` Marion & Christophe JAILLET
2020-04-11 10:17 ` Joe Perches
2020-04-11 10:27 ` Christophe JAILLET
2020-04-11 10:27 ` Christophe JAILLET
2020-04-10 19:34 ` 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=48f32229-068d-cc62-b6df-03cdc11b99a4@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--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).