Re: [PATCH v2] bonding: ban stacked bonding support

[Jay Vosburgh <jay.vosburgh@canonical.com>]

David Miller <davem@davemloft.net> wrote:

>From: Alexey Dobriyan <adobriyan@gmail.com>
>Date: Fri, 20 Mar 2015 20:46:38 +0300
>
>> If you add bonding master as a slave, and then release it,
>> it will no longer be an IFF_BONDING creating problems like described at
>> https://bugzilla.kernel.org/show_bug.cgi?id=89541
>> 
>> 	echo +bond1 >/sys/class/net/bonding_masters
>> 	echo 1 >/sys/class/net/bond1/bonding/mode
>> 	echo +bond2 >/sys/class/net/bonding_masters
>> 	echo +bond2 >/sys/class/net/bond1/bonding/slaves
>> 	echo -bond2 >/sys/class/net/bond1/bonding/slaves
>> 	echo -bond2 >/sys/class/net/bonding_masters
>> 
>> 	cat /proc/net/bonding/bond2	# should not exist
>> 		[oops]
>> 
>> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
>
>I feel like this has been brought up before and it was stated that
>some people are actually using things like this.
>
>I could be mistaken.

	I don't think you are.  I did a bit of checking after the
discussion last month and found a few relatively recent statements that
people were nesting bonds and it was apparently working, e.g.,

http://www.alexwitherspoon.com/debian-nested-bonded-interfaces/

	which, ironically, is exactly the case that would benefit from
not nesting the bonds, as 802.3ad would handle multiple aggregators
itself.

	However, there is also this discussion

http://lists.openwall.net/netdev/2011/01/22/66

	from netdev in 2011 that states that the ingress path of nested
bonds does not work, at least for the case described.  Perhaps some
configurations work and some don't.

	Let me see if I can run a quick test and see if this actually
works for me...

	-J

---
	-Jay Vosburgh, jay.vosburgh@canonical.com