From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: sachinp@in.ibm.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
ursula.braun@de.ibm.com, fubar@us.ibm.com
Subject: Re: [PATCH net-next-2.6] bonding: IGMP handling cleanup
Date: Thu, 18 Nov 2010 09:33:30 -0800 (PST) [thread overview]
Message-ID: <20101118.093330.39181120.davem@davemloft.net> (raw)
In-Reply-To: <1290077352.2781.47.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 18 Nov 2010 11:49:12 +0100
> Le jeudi 18 novembre 2010 à 11:26 +0100, Eric Dumazet a écrit :
>
>> 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.
>
> [PATCH net-next-2.6] bonding: IGMP handling cleanup
>
> Instead of iterating in_dev->mc_list from bonding driver, its better
> to call a helper function provided by igmp.c
> Details of implementation (locking) are private to igmp code.
>
> ip_mc_rejoin_group(struct ip_mc_list *im) becomes
> ip_mc_rejoin_groups(struct in_device *in_dev);
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> Cc: Jay Vosburgh <fubar@us.ibm.com>
> Cc: Sachin Sant <sachinp@in.ibm.com>
Applied, thanks Eric.
next prev parent reply other threads:[~2010-11-18 17:33 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 ` [PATCH net-2.6] bonding: fix a race in IGMP handling Eric Dumazet
2010-11-18 10:49 ` [PATCH net-next-2.6] bonding: IGMP handling cleanup Eric Dumazet
2010-11-18 17:33 ` David Miller [this message]
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=20101118.093330.39181120.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).