From: Nikolay Aleksandrov <nikolay@xxxxxxxxxxxxxxxxxxx> Date: Fri, 30 Mar 2018 13:46:17 +0300 > As previously discussed the recent changes break some setups and could lead > to packet drops. Thus the first patch reverts the behaviour for the bridge > to follow the minimum MTU but also keeps the ability to set the MTU to the > maximum (out of all ports) if vlan filtering is enabled. Patch 02 is the > bigger change in behaviour - we've always had trouble when configuring > bridges and their MTU which is auto tuning on port events > (add/del/changemtu), which means config software needs to chase it and fix > it after each such event, after patch 02 we allow the user to configure any > MTU (ETH_MIN/MAX limited) but once that is done the bridge stops auto > tuning and relies on the user to keep the MTU correct. > This should be compatible with cases that don't touch the MTU (or set it > to the same value), while allowing to configure the MTU and not worry > about it changing afterwards. > > The patches are intentionally split like this, so that if they get accepted > and there are any complaints patch 02 can be reverted. Series applied, thanks.
