From: Julia Lawall <julia.lawall@lip6.fr>
To: Kris Borer <kborer@gmail.com>
Cc: Gilles Muller <Gilles.Muller@lip6.fr>,
nicolas.palix@imag.fr, Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
cocci@systeme.lip6.fr
Subject: Re: [PATCH] coccinelle: add style check for assignment in if
Date: Sat, 15 Aug 2015 19:46:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1508151940330.2060@localhost6.localdomain6> (raw)
In-Reply-To: <CAMy_N62KRM6sBa_=sUYtMvLHZG75pJ07anLB8g5mrmzjxNCuvg@mail.gmail.com>
My version is below. It adds parentheses in a few more places, and allows
assignments without a binary operator (b) in the && cases.
Also I threw in a case for things like: if (ret = -ENOENT, !data)
Another thing is that the header is not really correct. It should be in
the following format:
/// Short comment of gernal interest
//# More information, eg about potential false positives
///
// Confidence: Moderate
// Copyright: whatever you want, it would be nice to have your name
// URL: http://coccinelle.lip6.fr/
// Comments:
// Options: --no-includes --include-headers
Then you should have:
virtual patch
Otherwise, the kernel infrastructure will not think that the patch mode is
supported. No other changes are needed, since no other modes are
supported. I don't think that supporting other modes is necessary, since
I think that checkpatch complains about this issue too.
julia
------------------------
// find checkpatch.pl errors of the type:
// ERROR: do not use assignment in if condition
//
// This script is designed to correct code where assignments exist in if
// conditions. It is only capable of handling a subset of such problems.
//
// For example:
//
// if(result = myfun())
//
// would become:
//
// result = myfun();
// if(result)
//
// Confidence: Moderate
// if ( (ret = call()) < 0 )
@if2@
expression i;
expression E, E2;
statement S1, S2;
binary operator b;
@@
+ i = E;
if (
(
... b
- (i = E)
+ i
|
- (i = E)
+ i
b ...
|
- (i = E)
+ i
|
- (i = E),
E2
)
) S1 else S2
// if ( ptr->fun && (ret = ptr->fun()) < 0 )
@if3@
expression i2;
expression E1, E2;
constant c;
binary operator b;
@@
+ if( E1 ) {
+ i2 = E2;
+ if (i2 b c) {
- if( E1 && ((i2 = E2) b c) ) {
...
- }
+ }
+ }
// if ( (ret = call()) < 0 && ret != -1 )
@if4@
expression i;
expression E, E2;
statement S1, S2;
binary operator b;
@@
+ i = E;
if (
(
(...
b
- (i = E)
+ i
)
|
(
- (i = E)
+ i
b
...)
|
- (i = E)
+ i
) && E2 ) S1 else S2
// if ( (ret = call()) < 0 && ret != -1 && ret != -2 )
@if5@
expression i;
expression E, E2, E3;
statement S1, S2;
binary operator b;
@@
+ i = E;
if (
(
(...
b
- (i = E)
+ i
)
|
(
- (i = E)
+ i
b
...)
|
- (i = E)
+ i
) && E2 && E3 ) S1 else S2
@@
expression i,e;
statement S1,S2;
@@
if (<+...
-i = e
+BAD
...+>) S1 else S2
prev parent reply other threads:[~2015-08-15 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 17:18 Kris Borer
2015-08-15 17:30 ` Julia Lawall
2015-08-15 17:33 ` Kris Borer
2015-08-15 17:46 ` Julia Lawall [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=alpine.DEB.2.02.1508151940330.2060@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=joe@perches.com \
--cc=kborer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
/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
all inboxes | Powered by JetHome®