Thread (12 messages) flat view 12 messages, 7 authors, 2012-08-10

Re: [net-next] bonding: don't allow the master to become its slave

From: David Miller <davem@davemloft.net>
Date: 2012-08-09 23:43:32

From: Jay Vosburgh <redacted>
Date: Thu, 09 Aug 2012 14:27:08 -0700
	If that's hard to do (and it might be; I'm not aware of a
standard way to run up and down those stacks of interfaces, which might
not always be vlans in the middle), there's still the priv_flags &
IFF_BONDING test that bonding could (and probably should) do itself as
well.  The team driver could presumably have a similar test, although I
seem to recall that team was allowed to nest.

	FWIW, I've seen both the top and bottom halves of that picture
in use (i.e., bonds consisting of vlans as slaves or bonds with vlans
configured above them), but not combined as in your diagram.
We're basically looking for cycles in a complex graph.

Some combination of Jay and Ben's most recent patches, with some minor
modifications, ought to do it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help