From: Jason Wang <jasowang@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 1/2] macvtap: slient sparse warnings
Date: Thu, 13 Jun 2013 14:27:56 +0800 [thread overview]
Message-ID: <51B9666C.7090108@redhat.com> (raw)
In-Reply-To: <1371102507.3252.96.camel@edumazet-glaptop>
On 06/13/2013 01:48 PM, Eric Dumazet wrote:
> On Thu, 2013-06-13 at 12:21 +0800, Jason Wang wrote:
>> This patch silents the following sparse warnings:
>>
>> dr
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/net/macvtap.c | 2 +-
>> include/linux/if_macvlan.h | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
>> index 992151c..acf55ba 100644
>> --- a/drivers/net/macvtap.c
>> +++ b/drivers/net/macvtap.c
>> @@ -429,7 +429,7 @@ static int macvtap_open(struct inode *inode, struct file *file)
>> if (!q)
>> goto out;
>>
>> - q->sock.wq = &q->wq;
>> + rcu_assign_pointer(q->sock.wq, &q->wq);
> Since nobody but you [1] can access this object at that time, you could
> rather use
> RCU_INIT_POINTER(q->sock.wq, &q->wq);
>
> rcu_assign_pointer() is also a documentation point (memory barrier)
>
> By using RCU_INIT_POINTER() you clearly show that you know you need no
> memory barrier.
>
True.
>> init_waitqueue_head(&q->wq.wait);
> [1] :
> or else, this init_waitqueue_head() should be done _before_ the
> rcu_asign_pointer()
Thanks, I will send v2 by using RCU_INIT_POINTER().
>
>> q->sock.type = SOCK_RAW;
>> q->sock.state = SS_CONNECTED;
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-06-13 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 4:21 [net-next PATCH 1/2] macvtap: slient sparse warnings Jason Wang
2013-06-13 4:21 ` [net-next PATCH 2/2] macvtap: fix uninitialized return value macvtap_ioctl_set_queue() Jason Wang
2013-06-13 5:48 ` [net-next PATCH 1/2] macvtap: slient sparse warnings Eric Dumazet
2013-06-13 6:27 ` Jason Wang [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=51B9666C.7090108@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).