From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sachin Sant <sachinp@in.ibm.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
ursula.braun@de.ibm.com, Jay Vosburgh <fubar@us.ibm.com>
Subject: [PATCH net-2.6] bonding: fix a race in IGMP handling
Date: Thu, 18 Nov 2010 11:26:18 +0100 [thread overview]
Message-ID: <1290075978.2781.36.camel@edumazet-laptop> (raw)
In-Reply-To: <1290073388.2781.12.camel@edumazet-laptop>
Le jeudi 18 novembre 2010 à 10:43 +0100, Eric Dumazet a écrit :
> Le jeudi 18 novembre 2010 à 10:33 +0100, Eric Dumazet a écrit :
> >
> >
> >
> > Hmm, sorry but this wont work.
> >
> > > diff -Narup linux-2.6-next/drivers/s390/net/lcs.c linux-2.6-next-new/drivers/s390/net/lcs.c
> > > --- linux-2.6-next/drivers/s390/net/lcs.c 2010-11-17 11:38:25.000000000 +0530
> > > +++ linux-2.6-next-new/drivers/s390/net/lcs.c 2010-11-18 11:59:46.000000000 +0530
> > > @@ -1269,10 +1269,10 @@ lcs_register_mc_addresses(void *data)
> > > in4_dev = in_dev_get(card->dev);
> > > if (in4_dev == NULL)
> > > goto out;
> > > - read_lock(&in4_dev->mc_list_lock);
> > > + rcu_read_lock();
> >
> > If you use rcu_read_lock(), then you also need to
> > use the rcu list iterators in lcs_remove_mc_addresses() and
> > lcs_set_mc_addresses()
> >
> > Then, its strange this driver is not protected by RTNL at this stage.
> >
> > Ah yes, it uses a kthread from its ndo_set_multicast_list() handler.
> >
> > This seems not safe at all.
Actually this raises an interesting case for bonding as well.
Before my RCU conversion __bond_resend_igmp_join_requests() was unsafe.
For net-next-2.6, it is now safe (RCU is held), but needs a cleanup
patch to avoid sparse errors.
Thanks
[PATCH net-2.6] bonding: fix a race in IGMP handling
RCU conversion in IGMP code done in net-next-2.6 raised a race in
__bond_resend_igmp_join_requests().
It iterates in_dev->mc_list without appropriate protection (RTNL, or
read_lock on in_dev->mc_list_lock).
Another cpu might delete an entry while we use it and trigger a fault.
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>
---
drivers/net/bonding/bond_main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index bdb68a6..71a1697 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -878,8 +878,10 @@ static void __bond_resend_igmp_join_requests(struct net_device *dev)
rcu_read_lock();
in_dev = __in_dev_get_rcu(dev);
if (in_dev) {
+ read_lock(&in_dev->mc_list_lock);
for (im = in_dev->mc_list; im; im = im->next)
ip_mc_rejoin_group(im);
+ read_unlock(&in_dev->mc_list_lock);
}
rcu_read_unlock();
next prev parent reply other threads:[~2010-11-18 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 9:18 [Patch -next] Adapt s390 qeth & lcs driver code to use RCU Sachin Sant
2010-11-18 9:33 ` Eric Dumazet
2010-11-18 9:43 ` Eric Dumazet
2010-11-18 10:26 ` Eric Dumazet [this message]
2010-11-18 10:49 ` [PATCH net-next-2.6] bonding: IGMP handling cleanup Eric Dumazet
2010-11-18 17:33 ` David Miller
2010-11-18 17:31 ` [PATCH net-2.6] bonding: fix a race in IGMP handling David Miller
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=1290075978.2781.36.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sachinp@in.ibm.com \
--cc=ursula.braun@de.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