[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110421192749.GA8732@midget.suse.cz>
Date: Thu, 21 Apr 2011 21:27:49 +0200
From: Jiri Bohac <jbohac@...e.cz>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Jiri Bohac <jbohac@...e.cz>, netdev@...r.kernel.org,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Jay Vosburgh <fubar@...ibm.com>,
Andy Gospodarek <andy@...yhouse.net>,
Benjamin Poirier <benjamin.poirier@...ymtl.ca>
Subject: Re: [PATCH] bonding: fix bridged bonds in 802.3ad mode
On Thu, Apr 21, 2011 at 08:08:19PM +0100, Ben Hutchings wrote:
> It seems to me that 1e253c3b8a1aeed51eef6fc366812f219b97de65 is bogus
> and should be reverted, rather than worked around by other drivers. We
> shouldn't enable non-conformant forwarding behaviour by default just
> because some people find it useful. The administrator should have to
> explicitly enable it.
This is what I thought as well. I find it even more awkward to
make this behaviour dependend on the STP setting of the bridge
(turning on STP works around this bonding problem, btw).
But even if forwarding of link-local frames is made optional in
some way, it will still break bonding when turned on. So unless
this it is completely reverted, we still need some kind of fix
for bonding.
Btw, this could also be fixed by checking for
skb->protocol == htons(ETH_P_SLOW) directly in the bridging code.
However, I think the wonderful rx_handler infrastructure makes it
much cleaner this way...
--
Jiri Bohac <jbohac@...e.cz>
SUSE Labs, SUSE CZ
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists