diff options
| author | Sven Eckelmann <sven@narfation.org> | 2016-10-22 09:46:24 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-10-26 17:19:07 -0400 |
| commit | 701470babace4c4bbcc8463a5609790f91f85bdb (patch) | |
| tree | 3468d1344b1e14378d18985af926817ea0b78951 /net/switchdev/switchdev.c | |
| parent | f806f772470d4b95df62a5d0f6e6cad5ccf49480 (diff) | |
batman-adv: Revert "use core MTU range checking in misc drivers"
The maximum MTU is defined via the slave devices of an batman-adv
interface. Thus it is not possible to calculate the max_mtu during the
creation of the batman-adv device when no slave devices are attached. Doing
so would for example break non-fragmentation setups which then
(incorrectly) allow an MTU of 1500 even when underlying device cannot
transport 1500 bytes + batman-adv headers.
Checking the dynamically calculated max_mtu via the minimum of the slave
devices MTU during .ndo_change_mtu is also used by the bridge interface.
Cc: Jarod Wilson <jarod@redhat.com>
Fixes: b3e3893e1253 ("net: use core MTU range checking in misc drivers")
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions