Messages in this thread | | | Date | Wed, 24 Nov 2010 17:45:42 -0800 | Subject | Re: [PATCH] bonding: check for assigned mac before adopting the slaves mac address | From | David Strand <> |
| |
We have a use case where we assign a mac to the bond device, because the slave device configuration may change periodically. With older kernels, it honored the assigned mac and everything was fine, with 2.6.36 it now uses the mac of whatever slave device is first instead of our assigned one.
ifenslave code and documentation appears to still support the old way, where a bond assigned mac will reign supreme, so this patch restores that behavior.
On Wed, Nov 24, 2010 at 3:33 PM, Jay Vosburgh <fubar@us.ibm.com> wrote: > How exactly is this a regression? The above referenced patch > changes the method used to decide if the bonding master needs to have > it's MAC address set. The original way was "bonding master's MAC is > zero," after the above, it's "adding first slave." > > Do you have some use case that manually sets the master's MAC > address prior to adding any slaves? > > -J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |