netdev - Re: [patch net-next 00/16] mlxsw: Handle changes in GRE configuration

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: <20171104.091601.318452211446664943.davem@davemloft.net>
Date:   Sat, 04 Nov 2017 09:16:01 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     jiri@...nulli.us
Cc:     netdev@...r.kernel.org, petrm@...lanox.com, idosch@...lanox.com,
        mlxsw@...lanox.com
Subject: Re: [patch net-next 00/16] mlxsw: Handle changes in GRE
 configuration

From: Jiri Pirko <jiri@...nulli.us>
Date: Fri,  3 Nov 2017 10:03:28 +0100

> From: Jiri Pirko <jiri@...lanox.com>
> 
> Petr says:
> 
> Until now, when an IP tunnel was offloaded by the mlxsw driver, the
> offload was pretty much static, and changes in Linux configuration were
> not reflected in the hardware. That led to discrepancies between traffic
> flows in slow path and fast path. The work-around used to be to remove
> all routes that forward to the netdevice and re-add them. This is
> clearly suboptimal, but actually, as of the decap-only patchset, it's
> not even enough anymore, and one needs to go all the way and simply drop
> the tunnel and recreate it correctly.
> 
> With this patchset, the NETDEV_CHANGE events that are generated for
> changes of up'd tunnel netdevices are captured and interpreted to
> correctly reconfigure the HW in accordance with changes requested at the
> software layer. In addition, NETDEV_CHANGEUPPER, NETDEV_UP and
> NETDEV_DOWN are now handled not only for tunnel devices themselves, but
> also for their bound devices.
 ...

Series applied, thanks Jiri.