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: <562FDE96.3030400@gmail.com>
Date:	Tue, 27 Oct 2015 13:29:10 -0700
From:	Alexander Duyck <alexander.duyck@...il.com>
To:	Brian Rak <brak@...eservers.com>, netdev@...r.kernel.org
Subject: Re: Missing IPv4 routes

On 10/27/2015 01:01 PM, Brian Rak wrote:
> (Existing email got kinda messy, starting over again):
>
> So, I'm having an issue with the kernel where if I add a bunch of 
> routes, I see some of them go "missing".  They don't show up in the 
> 'ip -4 route' list, but they do show up if I do 'ip -4 route get X'.
>
> I managed to come up with a simple set of reproduction commands:
>
> ip link add veth0 type veth peer name veth1
> ip link set veth0 up
> ip link set veth1 up
>
> ip route add 108.61.171.119/32 dev veth0  scope link
> ip route add 108.61.171.141/32 dev veth1  scope link
> ip route add 108.61.171.223/32 dev veth1  scope link
> ip route add 108.61.171.250/32 dev veth1  scope link
> ip route add 108.61.171.247/32 dev veth1  scope link
>
> ip route show
>
> In the route show, you'll see 108.61.171.250/32 and 108.61.171.247/32 
> missing completely.
>
> I did a lot of bisecting, and traced it down to this commit:
>
> commit 8be33e955cb959dabc1a6eef0b7356fe8cf73fa6
> Author: Alexander Duyck <alexander.h.duyck@...hat.com>
> Date:   Wed Mar 4 14:59:19 2015 -0800
>
>     fib_trie: Fib walk rcu should take a tnode and key instead of a 
> trie and a leaf
>
> The commit immediately prior to this one 
> (7289e6ddb633aaee6ccea2bd2e410654c47b29a6) works fine.
>
> I tried the off-by-one fix from 
> e55ffaf457bcc8ec4e9d9f56f955971f834d65b3, however this doesn't appear 
> to help at all.   This code is a little above my head, so I don't 
> really understand what exactly is broken here.

I'll take a look at it and see if I can come up with a fix by this 
afternoon.

Thanks.

- Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ