ethernet: T3871: leave a bond member's MTU alone while it is still enslaved

Deleting the ethernet configuration of a member of a jumbo bond dropped that
member to the default MTU while the bond went on using it at 9000. It stayed
the active slave, so jumbo frames were discarded in both directions, small
ones passed, and nothing was logged.

A bond owns its members' MTU just as it owns their address - the ethernet
path already refuses to let a member set either, and says so. The reset now
waits, like the address, until the bond has released the port.

The bonding smoketest covers both halves on a running system: while the
member is enslaved it must keep the bond's address and MTU, and once the
bond releases it, it must get its own address and the default MTU back.

0 files changed, 0 insertions, 0 deletions