From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-he1eur01on0078.outbound.protection.outlook.com ([104.47.0.78]:16568 "EHLO EUR01-HE1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751319AbeCVRyL (ORCPT ); Thu, 22 Mar 2018 13:54:11 -0400 From: Ido Schimmel To: netdev@vger.kernel.org Cc: davem@davemloft.net, jiri@mellanox.com, lucien.xin@gmail.com, mlxsw@mellanox.com, Ido Schimmel Subject: [PATCH net 0/3] mlxsw: Handle changes to MTU in GRE tunnels Date: Thu, 22 Mar 2018 19:53:32 +0200 Message-Id: <20180322175335.26232-1-idosch@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain Sender: netdev-owner@vger.kernel.org List-ID: 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. Petr Machata (3): ip_tunnel: Emit events for post-register MTU changes mlxsw: spectrum_router: Move mlxsw_sp_rif_ipip_lb_op() mlxsw: spectrum_router: Handle MTU change of GRE netdevs .../net/ethernet/mellanox/mlxsw/spectrum_router.c | 78 ++++++++++++++-------- net/ipv4/ip_tunnel.c | 26 ++++++-- 2 files changed, 72 insertions(+), 32 deletions(-) -- 2.14.3