From: Matthew Wilcox <willy@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Joe Perches <joe@perches.com>, Rao Shoaib <rao.shoaib@oracle.com>,
Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org, brouer@redhat.com,
linux-mm@kvack.org
Subject: Re: [PATCH 1/2] Move kfree_call_rcu() to slab_common.c
Date: Thu, 4 Jan 2018 16:07:07 -0800 [thread overview]
Message-ID: <20180105000707.GA22237@bombadil.infradead.org> (raw)
In-Reply-To: <20180104234732.GM9671@linux.vnet.ibm.com>
On Thu, Jan 04, 2018 at 03:47:32PM -0800, Paul E. McKenney wrote:
> I was under the impression that typeof did not actually evaluate its
> argument, but rather only returned its type. And there are a few macros
> with this pattern in mainline.
>
> Or am I confused about what typeof does?
I think checkpatch is confused by the '*' in the typeof argument:
$ git diff |./scripts/checkpatch.pl --strict
CHECK: Macro argument reuse 'ptr' - possible side-effects?
#29: FILE: include/linux/rcupdate.h:896:
+#define kfree_rcu(ptr, rcu_head) \
+ __kfree_rcu(&((ptr)->rcu_head), offsetof(typeof(*(ptr)), rcu_head))
If one removes the '*', the warning goes away.
I'm no perlista, but Joe, would this regexp modification make sense?
+++ b/scripts/checkpatch.pl
@@ -4957,7 +4957,7 @@ sub process {
next if ($arg =~ /\.\.\./);
next if ($arg =~ /^type$/i);
my $tmp_stmt = $define_stmt;
- $tmp_stmt =~ s/\b(typeof|__typeof__|__builtin\w+|typecheck\s*\(\s*$Type\s*,|\#+)\s*\(*\s*$arg\s*\)*\b//g;
+ $tmp_stmt =~ s/\b(typeof|__typeof__|__builtin\w+|typecheck\s*\(\s*$Type\s*,|\#+)\s*\(*\**\(*\s*$arg\s*\)*\b//g;
$tmp_stmt =~ s/\#+\s*$arg\b//g;
$tmp_stmt =~ s/\b$arg\s*\#\#//g;
my $use_cnt = $tmp_stmt =~ s/\b$arg\b//g;
next prev parent reply other threads:[~2018-01-05 0:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 20:11 [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
2018-01-02 20:11 ` [PATCH 2/2] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures rao.shoaib
2018-01-02 22:23 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c Matthew Wilcox
2018-01-02 22:49 ` Rao Shoaib
2018-01-04 1:38 ` Boqun Feng
2018-01-04 20:35 ` Rao Shoaib
2018-01-04 21:27 ` Rao Shoaib
2018-01-04 21:46 ` Matthew Wilcox
2018-01-04 22:18 ` Rao Shoaib
2018-01-04 23:13 ` Matthew Wilcox
2018-01-04 23:47 ` Paul E. McKenney
2018-01-05 0:07 ` Matthew Wilcox [this message]
2018-01-05 2:14 ` Rao Shoaib
2018-01-05 6:46 ` Joe Perches
2018-03-27 1:56 ` Rao Shoaib
2018-03-27 2:06 ` Joe Perches
2018-04-02 5:31 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-02 5:31 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
2018-04-02 7:59 ` kbuild test robot
2018-04-02 9:45 ` kbuild test robot
2018-04-02 15:43 ` Paul E. McKenney
2018-04-03 17:22 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-03 17:22 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
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=20180105000707.GA22237@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=brouer@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rao.shoaib@oracle.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 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).