netdev - [BISECTED] Re: Strange ARP behaviour with VXLAN

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, 7 Feb 2017 12:12:38 +0000
From:   Edward Cree <ecree@...arflare.com>
To:     netdev <netdev@...r.kernel.org>
CC:     Pravin B Shelar <pshelar@....org>, Jiri Benc <jbenc@...hat.com>
Subject: [BISECTED] Re: Strange ARP behaviour with VXLAN

On 01/02/17 16:20, Edward Cree wrote:
> [ Specific kernel version: 624374a56419c2d6d428c862f32cc1b20519095d.
> Note that if I do the same on 3.10.327-el7.x86_64 (RHEL7u2) the problem
> does not occur.  I have not yet tested on older mainline kernels, but plan
> to do so shortly.  Also note that in both cases, the link partner is running
> 3.10.327-el7.x86_64. ]
I've now bisected this to 272d96a5ab10 "net: vxlan: lwt: Use source ip address
 during route lookup."  Which is interesting, because I'm using a vxlan
 netdevice, not an LWT; maybe in the former case the saddr is bogus.
Presumably the route lookup gets cached and that's why it remembers the broken
 state.

-Ed