diff options
author | Jarod Wilson <jarod@redhat.com> | 2017-03-06 08:48:58 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-03-08 22:19:17 -0800 |
commit | 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 (patch) | |
tree | 1a733746b224f8bf201607ac38d98a77b85642f9 /fs/exec.c | |
parent | aac1561ad98e74f6ea43337f9b9714ab0b1f493e (diff) | |
download | linux-3331aa378e9bcbd0d16de9034b0c20f4050e26b4.tar.bz2 |
team: use ETH_MAX_MTU as max mtu
This restores the ability to set a team device's mtu to anything higher
than 1500. Similar to the reported issue with bonding, the team driver
calls ether_setup(), which sets an initial max_mtu of 1500, while the
underlying hardware can handle something much larger. Just set it to
ETH_MAX_MTU to support all possible values, and the limitations of the
underlying devices will prevent setting anything too large.
Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
CC: Cong Wang <xiyou.wangcong@gmail.com>
CC: Jiri Pirko <jiri@resnulli.us>
CC: netdev@vger.kernel.org
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/exec.c')
0 files changed, 0 insertions, 0 deletions