openvswitch: Set internal device max mtu to ETH_MAX_MTU.
authorJarno Rajahalme <jarno@ovn.org>
Wed, 15 Feb 2017 05:16:28 +0000 (21:16 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 14 May 2017 12:08:30 +0000 (14:08 +0200)
commit853151191ef2b62fa02c4a9fdeb90a8baeb3d911
tree982a133dae30d896ab652124c9aa634bda8c1473
parent8656ebcc28bc2a2338c1dc9a7f5de10c80e3cc1e
openvswitch: Set internal device max mtu to ETH_MAX_MTU.

[ Upstream commit 425df17ce3a26d98f76e2b6b0af2acf4aeb0b026 ]

Commit 91572088e3fd ("net: use core MTU range checking in core net
infra") changed the openvswitch internal device to use the core net
infra for controlling the MTU range, but failed to actually set the
max_mtu as described in the commit message, which now defaults to
ETH_DATA_LEN.

This patch fixes this by setting max_mtu to ETH_MAX_MTU after
ether_setup() call.

Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
Signed-off-by: Jarno Rajahalme <jarno@ovn.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/openvswitch/vport-internal_dev.c