From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Jan Engelhardt <jengelh@inai.de>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
netfilter-devel@vger.kernel.org, kaber@trash.net,
pablo@netfilter.org
Subject: Re: [iptables PATCH] list: fix prefetch dummy
Date: Tue, 07 Apr 2015 10:45:32 -0700 [thread overview]
Message-ID: <552417BC.6050807@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1504071036001.29221@nerf40.vanv.qr>
On 04/07/2015 01:37 AM, Jan Engelhardt wrote:
> On Tuesday 2015-04-07 02:38, Alexander Duyck wrote:
>
>> On 04/06/2015 11:05 AM, Arturo Borrero Gonzalez wrote:
>>> linux_list.h:381:59: warning: right-hand operand of comma expression has no effect [-Wunused-value]
>>> for (pos = list_entry((head)->next, typeof(*pos), member), \
>>> ^
>>> libiptc.c:552:2: note: in expansion of macro 'list_for_each_entry'
>>> list_for_each_entry(c, &h->chains, list) {
>>> ^
>>>
>>> [ Patch copied from one similar of Patrick McHardy on libnftnl ]
>>>
>>> Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
>>> ---
>>> libiptc/linux_list.h | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/libiptc/linux_list.h b/libiptc/linux_list.h
>>> index abdcf88..559e33c 100644
>>> --- a/libiptc/linux_list.h
>>> +++ b/libiptc/linux_list.h
>>> @@ -27,7 +27,7 @@
>>> 1; \
>>> })
>>>
>>> -#define prefetch(x) 1
>>> +#define prefetch(x) ((void)0)
>>>
>>> /* empty define to make this work in userspace -HW */
>>> #define smp_wmb()
>>>
>> Why not just use "do {} while (0)"? I know that is what is used in the
>> kernel for functions that don't do anything.
> I may be getting the terms wrong, but:
> do{}while(0) is not an expression, it is a (block) control statement.
> In particular, do{}while(0) won't evaluate to an rvalue.
Right. That is the point in this case. I am assuming what Arturo is
trying to accomplish since you shouldn't be able to evaluate ((void)0)
as an rvalue either.
The prefetch(x) is an empty statement which is being cast as a void to
avoid a compiler warning, so it falls into the first case as defined in:
http://kernelnewbies.org/FAQ/DoWhile0
- Alex
next prev parent reply other threads:[~2015-04-07 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 18:05 [iptables PATCH] list: fix prefetch dummy Arturo Borrero Gonzalez
2015-04-07 0:38 ` Alexander Duyck
2015-04-07 8:37 ` Jan Engelhardt
2015-04-07 17:45 ` Alexander Duyck [this message]
2015-04-07 18:17 ` Jan Engelhardt
2015-04-07 19:29 ` Alexander Duyck
2015-04-08 17:04 ` Pablo Neira Ayuso
2015-04-09 0:18 ` Stephen Hemminger
2015-04-09 10:45 ` Pablo Neira Ayuso
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=552417BC.6050807@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=arturo.borrero.glez@gmail.com \
--cc=jengelh@inai.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).