netdev - Re: [PATCH net 0/3] mlxsw: Handle changes to MTU in GRE tunnels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180323.125631.1663564310512844945.davem@davemloft.net>
Date:   Fri, 23 Mar 2018 12:56:31 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, lucien.xin@...il.com,
        mlxsw@...lanox.com
Subject: Re: [PATCH net 0/3] mlxsw: Handle changes to MTU in GRE tunnels

From: Ido Schimmel <idosch@...lanox.com>
Date: Thu, 22 Mar 2018 19:53:32 +0200

> 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.

Series applied, thanks.