Re: [PATCH v3] bonding: Inactive slaves should keep inactive flag's value

From: David Miller
Date: Fri Apr 04 2014 - 10:03:43 EST


From: Zheng Li <zheng.x.li@xxxxxxxxxx>
Date: Wed, 2 Apr 2014 11:01:48 +0800

> bond_open is not setting the inactive flag correctly for some modes (alb and
> tlb), resulting in error behavior if the bond has been administratively set
> down and then back up. This effect should not occur when slaves are added while
> the bond is up; it's something that only happens after a down/up bounce of the
> bond.
>
> For example, in bond tlb or alb mode, domu send some ARP request which go out
> from dom0 bond's active slave, then the ARP broadcast request packets go back to
> inactive slave from switch, because the inactive slave's inactive flag is zero,
> kernel will receive the packets and pass them to bridge that cause dom0's bridge
> map domu's MAC address to port of bond, bridge should map domu's MAC to port of
> vif.
>
> Signed-off-by: Zheng Li <zheng.x.li@xxxxxxxxxx>
> Signed-off-by: Jay Vosburgh <j.vosburgh@xxxxxxxxx>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/