From: Jiri Benc <jbenc@redhat.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>,
dcbw@redhat.com
Subject: Re: [PATCH net] ipvlan: fix addr hash list corruption
Date: Wed, 25 Mar 2015 09:58:51 +0100 [thread overview]
Message-ID: <20150325095851.1d8d1622@griffin> (raw)
In-Reply-To: <CAF2d9jh+VozezamrEK_6vfTvY8LZSzw9n-bJjSX3G11RXmfz3w@mail.gmail.com>
On Tue, 24 Mar 2015 16:16:38 -0700, Mahesh Bandewar wrote:
> Well, we already have hlist_unhashed().The following patch should fix
> the duplicate addition as well as deletion. Please give it a try.
Good idea, it's surely better than adding a new boolean.
However, I'm wondering that when there's apparently no problem with the
addresses being on the hash list when interface is down, what's the
point in clearing the hash list in the ndo_stop handler and
repopulating it in ndo_open?
The following patch fixes the problem, too, and as a bonus removes code:
diff --git a/drivers/net/ipvlan/ipvlan_main.c b/drivers/net/ipvlan/ipvlan_main.c
index 4f4099d5603d..03def841b1a9 100644
--- a/drivers/net/ipvlan/ipvlan_main.c
+++ b/drivers/net/ipvlan/ipvlan_main.c
@@ -149,10 +149,6 @@ static int ipvlan_open(struct net_device *dev)
else
dev->flags &= ~IFF_NOARP;
- if (ipvlan->ipv6cnt > 0 || ipvlan->ipv4cnt > 0) {
- list_for_each_entry(addr, &ipvlan->addrs, anode)
- ipvlan_ht_addr_add(ipvlan, addr);
- }
return dev_uc_add(phy_dev, phy_dev->dev_addr);
}
@@ -166,11 +162,6 @@ static int ipvlan_stop(struct net_device *dev)
dev_mc_unsync(phy_dev, dev);
dev_uc_del(phy_dev, phy_dev->dev_addr);
-
- if (ipvlan->ipv6cnt > 0 || ipvlan->ipv4cnt > 0) {
- list_for_each_entry(addr, &ipvlan->addrs, anode)
- ipvlan_ht_addr_del(addr, !dev->dismantle);
- }
return 0;
}
What do you think? Should I submit this formally?
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-03-25 8:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 21:10 [PATCH net] ipvlan: fix addr hash list corruption Jiri Benc
2015-03-24 1:10 ` Mahesh Bandewar
2015-03-24 8:58 ` Jiri Benc
2015-03-24 17:00 ` David Miller
2015-03-24 17:06 ` Jiri Benc
2015-03-24 23:16 ` Mahesh Bandewar
2015-03-25 1:18 ` David Miller
2015-03-25 8:58 ` Jiri Benc [this message]
2015-03-25 15:46 ` David Miller
2015-03-25 18:11 ` Mahesh Bandewar
2015-03-25 18:47 ` Dan Williams
2015-03-25 23:21 ` Jiri Benc
2015-03-25 23:49 ` Jiri Benc
2015-03-26 2:15 ` Mahesh Bandewar
2015-03-26 8:45 ` Jiri Benc
2015-03-27 5:00 ` Mahesh Bandewar
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=20150325095851.1d8d1622@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=maheshb@google.com \
--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).