From: Pravin Shelar <pshelar@nicira.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
Thomas Richter <tmricht@linux.vnet.ibm.com>,
Mike Rapoport <mike.rapoport@ravellosystems.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] vxlan: fix rcu related warnings
Date: Wed, 31 Jul 2013 10:57:14 -0700 [thread overview]
Message-ID: <CALnjE+obgWjqDhuyWUJ=kimMKQbbweenRdxbU1ZCBWBP_qe8Zg@mail.gmail.com> (raw)
In-Reply-To: <20130730173516.3d536077@nehalam.linuxnetplumber.net>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Tue, Jul 30, 2013 at 5:35 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Tue, 30 Jul 2013 16:04:59 -0700
> Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>> On Tue, 2013-07-30 at 16:02 -0700, Stephen Hemminger wrote:
>>
>> > Which version of sparse? I don't see this with latest version.
>>
>> Make sure you have CONFIG_SPARSE_RCU_POINTER=y
>>
>>
>
> I have it enabled. And am using latest version from git.
Attached patch fixes warnings for me.
[-- Attachment #2: 0002-vxlan-fix-rcu-warn.patch --]
[-- Type: application/octet-stream, Size: 877 bytes --]
From 805650bc435b99cbcc02829039a0c3a877416fd9 Mon Sep 17 00:00:00 2001
From: Pravin B Shelar <pshelar@nicira.com>
Date: Wed, 31 Jul 2013 10:52:59 -0700
Subject: [PATCH net-next] vxlan: fix rcu warn.
---
drivers/net/vxlan.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index 31718c6..e4d1513 100644
--- a/drivers/net/vxlan.c
+++ b/drivers/net/vxlan.c
@@ -176,7 +176,7 @@ static inline struct hlist_head *vs_head(struct net *net, __be16 port)
/* First remote destination for a forwarding entry.
* Guaranteed to be non-NULL because remotes are never deleted.
*/
-static inline struct vxlan_rdst __rcu *first_remote_rcu(struct vxlan_fdb *fdb)
+static inline struct vxlan_rdst *first_remote_rcu(struct vxlan_fdb *fdb)
{
return list_entry_rcu(fdb->remotes.next, struct vxlan_rdst, list);
}
--
1.7.1
next prev parent reply other threads:[~2013-07-31 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 20:18 [PATCH net-next] vxlan: fix rcu related warnings Stephen Hemminger
2013-07-30 22:17 ` Pravin Shelar
2013-07-30 23:02 ` Stephen Hemminger
2013-07-30 23:04 ` Eric Dumazet
2013-07-31 0:35 ` Stephen Hemminger
2013-07-31 17:57 ` Pravin Shelar [this message]
2013-08-05 0:17 ` [PATCH net-next v3] vxlan: fix rcu related warning Stephen Hemminger
2013-08-05 1:47 ` David Miller
2013-07-30 23:20 ` [PATCH net-next] vxlan: fix rcu related warnings Pravin Shelar
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='CALnjE+obgWjqDhuyWUJ=kimMKQbbweenRdxbU1ZCBWBP_qe8Zg@mail.gmail.com' \
--to=pshelar@nicira.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mike.rapoport@ravellosystems.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tmricht@linux.vnet.ibm.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).