netdev - Re: [PATCH net v3 0/4] vxlan: Various fixes

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]

Date:   Tue, 18 Dec 2018 21:19:20 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     petrm@...lanox.com
Cc:     netdev@...r.kernel.org, idosch@...lanox.com,
        roopa@...ulusnetworks.com
Subject: Re: [PATCH net v3 0/4] vxlan: Various fixes

From: Petr Machata <petrm@...lanox.com>
Date: Tue, 18 Dec 2018 13:15:57 +0000

> This patch set contains three fixes for the vxlan driver.
> 
> Patch #1 fixes handling of offload mark on replaced VXLAN FDB entries. A
> way to trigger this is to replace the FDB entry with one that can not be
> offloaded. A future patch set should make it possible to veto such FDB
> changes. However the FDB might still fail to be offloaded due to another
> issue, and the offload mark should reflect that.
> 
> Patch #2 fixes problems in __vxlan_dev_create() when a call to
> rtnl_configure_link() fails. These failures would be tricky to hit on a
> real system, the most likely vector is through an error in vxlan_open().
> However, with the abovementioned vetoing patchset, vetoing the created
> entry would trigger the same problems (and be easier to reproduce).
> 
> Patch #3 fixes a problem in vxlan_changelink(). In situations where the
> default remote configured in the FDB table (if any) does not exactly
> match the remote address configured at the VXLAN device, changing the
> remote address breaks the default FDB entry. Patch #4 is then a self
> test for this issue.
 ...

Series applied, thank you.