net: remove MTU limits on a few ether_setup callers
These few drivers call ether_setup(), but have no ndo_change_mtu, and thus were overlooked for changes to MTU range checking behavior. They previously had no range checks, so for feature-parity, set their min_mtu to 0 and max_mtu to ETH_MAX_MTU (65535), instead of the 68 and 1500 inherited from the ether_setup() changes. Fine-tuning can come after we get back to full feature-parity here. CC: netdev@vger.kernel.org Reported-by:Asbjoern Sloth Toennesen <asbjorn@asbjorn.st> CC: Asbjoern Sloth Toennesen <asbjorn@asbjorn.st> CC: R Parameswaran <parameswaran.r7@gmail.com> Signed-off-by:
Jarod Wilson <jarod@redhat.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- net/atm/br2684.c 3 additions, 1 deletionnet/atm/br2684.c
- net/bluetooth/bnep/netdev.c 2 additions, 0 deletionsnet/bluetooth/bnep/netdev.c
- net/dsa/slave.c 2 additions, 0 deletionsnet/dsa/slave.c
- net/irda/irlan/irlan_eth.c 2 additions, 1 deletionnet/irda/irlan/irlan_eth.c
- net/l2tp/l2tp_eth.c 2 additions, 0 deletionsnet/l2tp/l2tp_eth.c
Loading
Please register or sign in to comment