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 <email address hidden>
CC: Jiri Pirko <email address hidden>
CC: <email address hidden>
Signed-off-by: Jarod Wilson <email address hidden>
Signed-off-by: David S. Miller <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
This fix was merged and landed in 4.10.5
commit be18cce7e665b09 406c4168fd3da32 492dd5d8f3
Author: Jarod Wilson <email address hidden>
Date: Mon Mar 6 08:48:58 2017 -0500
team: use ETH_MAX_MTU as max mtu
[ Upstream commit 3331aa378e9bcbd 0d16de9034b0c20 f4050e26b4 ]
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 <email address hidden>
CC: Jiri Pirko <email address hidden>
CC: <email address hidden>
Signed-off-by: Jarod Wilson <email address hidden>
Signed-off-by: David S. Miller <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>