summaryrefslogtreecommitdiffstats
path: root/drivers/net/team
diff options
context:
space:
mode:
authorJarod Wilson <jarod@redhat.com>2017-03-06 14:48:58 +0100
committerDavid S. Miller <davem@davemloft.net>2017-03-09 07:19:17 +0100
commit3331aa378e9bcbd0d16de9034b0c20f4050e26b4 (patch)
tree1a733746b224f8bf201607ac38d98a77b85642f9 /drivers/net/team
parentnet: Revert ksettings conversions. (diff)
downloadlinux-3331aa378e9bcbd0d16de9034b0c20f4050e26b4.tar.xz
linux-3331aa378e9bcbd0d16de9034b0c20f4050e26b4.zip
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 'drivers/net/team')
-rw-r--r--drivers/net/team/team.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c
index 4a24b5d15f5a..1b52520715ae 100644
--- a/drivers/net/team/team.c
+++ b/drivers/net/team/team.c
@@ -2072,6 +2072,7 @@ static int team_dev_type_check_change(struct net_device *dev,
static void team_setup(struct net_device *dev)
{
ether_setup(dev);
+ dev->max_mtu = ETH_MAX_MTU;
dev->netdev_ops = &team_netdev_ops;
dev->ethtool_ops = &team_ethtool_ops;