Commit be18cce7 authored by Jarod Wilson's avatar Jarod Wilson Committed by Greg Kroah-Hartman

team: use ETH_MAX_MTU as max mtu

[ Upstream commit 3331aa37 ]

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: 91572088 ("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: default avatarJarod Wilson <jarod@redhat.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 92ab4dea
...@@ -2075,6 +2075,7 @@ static int team_dev_type_check_change(struct net_device *dev, ...@@ -2075,6 +2075,7 @@ static int team_dev_type_check_change(struct net_device *dev,
static void team_setup(struct net_device *dev) static void team_setup(struct net_device *dev)
{ {
ether_setup(dev); ether_setup(dev);
dev->max_mtu = ETH_MAX_MTU;
dev->netdev_ops = &team_netdev_ops; dev->netdev_ops = &team_netdev_ops;
dev->ethtool_ops = &team_ethtool_ops; dev->ethtool_ops = &team_ethtool_ops;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment