diff options
author | David S. Miller <davem@davemloft.net> | 2018-03-23 12:54:35 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-03-23 12:54:35 -0400 |
commit | 69ebaed0c6b5f52d2dc15fb164bc2b2619ae04b9 (patch) | |
tree | 9a99f5aff54c9be0d4fee49c47dddfb4e67763b9 /net/netfilter | |
parent | f36b7534b83357cf52e747905de6d65b4f7c2512 (diff) | |
parent | 68c3cd925597842c4744fd93d61f8cd2496cdfc8 (diff) | |
download | linux-stable-69ebaed0c6b5f52d2dc15fb164bc2b2619ae04b9.tar.gz linux-stable-69ebaed0c6b5f52d2dc15fb164bc2b2619ae04b9.tar.bz2 linux-stable-69ebaed0c6b5f52d2dc15fb164bc2b2619ae04b9.zip |
Merge branch 'mlxsw-GRE-mtu-changes'
Ido Schimmel says:
====================
mlxsw: Handle changes to MTU in GRE tunnels
Petr says:
When offloading GRE tunnels, the MTU setting is kept fixed after the
initial offload even as the slow-path configuration changed. Worse: the
offloaded MTU setting is actually just a transient value set at the time
of NETDEV_REGISTER of the tunnel. As of commit ffc2b6ee4174 ("ip_gre:
fix IFLA_MTU ignored on NEWLINK"), that transient value is zero, and
unless there's e.g. a VRF migration that prompts re-offload, it stays at
zero, and all GRE packets end up trapping.
Thus, in patch #1, change the way the MTU is changed post-registration,
so that the full event protocol is observed. That way the drivers get to
see the change and have a chance to react.
In the remaining two patches, implement support for MTU change in mlxsw
driver.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/netfilter')
0 files changed, 0 insertions, 0 deletions