From: Joe Eykholt <jre@nuovasystems.com>
To: David Miller <davem@davemloft.net>
Cc: jgarzik@pobox.com, fubar@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 5/5] net/core: Allow receive on active slaves.
Date: Sat, 19 Jul 2008 21:20:37 -0700 [thread overview]
Message-ID: <4882BD15.70303@nuovasystems.com> (raw)
In-Reply-To: <20080705.213818.71574869.davem@davemloft.net>
David Miller wrote:
> From: Joe Eykholt <jre@nuovasystems.com>
> Date: Sat, 05 Jul 2008 21:36:42 -0700
>
>> David Miller wrote:
>>> From: Jeff Garzik <jgarzik@pobox.com>
>>> Date: Fri, 04 Jul 2008 08:45:52 -0400
>>>
>>>> Jay Vosburgh wrote:
>>>>> @@ -2104,7 +2104,8 @@ int netif_receive_skb(struct sk_buff *skb)
>>>>> #endif
>>>>>
>>>>> list_for_each_entry_rcu(ptype, &ptype_all, list) {
>>>>> - if (ptype->dev == null_or_orig || ptype->dev == skb->dev) {
>>>>> + if (ptype->dev == null_or_orig || ptype->dev == skb->dev ||
>>>>> + ptype->dev == orig_dev) {
>>>>> if (pt_prev)
>>>>> ret = deliver_skb(skb, pt_prev, orig_dev);
>>>>> pt_prev = ptype;
>>>>> @@ -2129,7 +2130,8 @@ ncls:
>>>>> list_for_each_entry_rcu(ptype,
>>>>> &ptype_base[ntohs(type) & PTYPE_HASH_MASK], list) {
>>>>> if (ptype->type == type &&
>>>>> - (ptype->dev == null_or_orig || ptype->dev == skb->dev)) {
>>>>> + (ptype->dev == null_or_orig || ptype->dev == skb->dev ||
>>>>> + ptype->dev == orig_dev)) {
>>>>> if (pt_prev)
>>>> This needs a review&ack from David, then OK...
>>> I fear this bit of the changes will break AF_PACKET device binding.
>>> So for example, if a tap registers it wants to hear eth0, it will now
>>> hear bond0 as well as eth0 if eth0 is a part of bond0.
>> Each ptype will get matched and delivered to at most once. So if
>> someone binds AF_PACKET to only eth0, they'll only see the packet once.
>> Whereas before patch 4, the frame wouldn't be delivered to them
>> at all, since skb->dev has already been changed to the bond.
>
> Ok, that works.
>
> Jeff, I ACK this patch and the others that go with it:
>
> Acked-by: David S. Miller <davem@davemloft.net>
Is there something more that I need to do to get this integrated?
Do I need to refresh the patches or something?
Will it go in during the next merge window?
Thanks,
Joe
next prev parent reply other threads:[~2008-07-20 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 1:21 [PATCH net-next-2.6 0/5] bonding: Refactor, fix, and updates Jay Vosburgh
2008-07-03 1:21 ` [PATCH 1/5] bonding: refactor mii monitor Jay Vosburgh
2008-07-03 1:21 ` [PATCH 2/5] bonding: Don't destroy bonding master when removing slave via sysfs Jay Vosburgh
2008-07-03 1:22 ` [PATCH 3/5] net/core: Uninline skb_bond() Jay Vosburgh
2008-07-03 1:22 ` [PATCH 4/5] net/core: Allow certain receives on inactive slave Jay Vosburgh
2008-07-03 1:22 ` [PATCH 5/5] net/core: Allow receive on active slaves Jay Vosburgh
2008-07-04 12:45 ` Jeff Garzik
2008-07-06 4:12 ` David Miller
2008-07-06 4:36 ` Joe Eykholt
2008-07-06 4:38 ` David Miller
2008-07-20 4:20 ` Joe Eykholt [this message]
2008-08-07 8:00 ` [PATCH 1/5] bonding: refactor mii monitor Jeff Garzik
2008-08-06 22:49 ` [PATCH net-next-2.6 0/5] bonding: Refactor, fix, and updates Jay Vosburgh
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=4882BD15.70303@nuovasystems.com \
--to=jre@nuovasystems.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.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).