On Sun, Jan 25, 2026 at 08:21:08PM +0900, Tetsuo Handa wrote:
We would need to update team driver side not to trigger dev_set_mtu().
Below diff passed the reproducer, but I don't know whether it is safe
to trigger dev_set_mtu() for team_uninit() and team_del_slave() and
the err_port_enter: label of team_port_add()...
I just checked and the same issue was fixed in the bond driver in commit
f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when unregistering
slave"), so I would try a similar fix in team.
A solution in the core would be better, but I don't know if it's
possible and the blast radius would also be bigger, so it's something to
think about for net-next.