From: Brian Rak <brak@gameservers.com>
To: Alexander Duyck <alexander.duyck@gmail.com>, netdev@vger.kernel.org
Subject: Re: Missing IPv4 routes
Date: Tue, 27 Oct 2015 16:01:36 -0400 [thread overview]
Message-ID: <562FD820.5050901@gameservers.com> (raw)
In-Reply-To: <562E5B69.6080108@vultr.com>
(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@redhat.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.
next prev parent reply other threads:[~2015-10-27 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 21:34 Missing IPv4 routes Brian Rak
2015-10-23 22:32 ` Alexander Duyck
2015-10-24 13:32 ` Brian Rak
2015-10-26 15:28 ` Alexander Duyck
2015-10-26 16:57 ` Brian Rak
2015-10-27 20:01 ` Brian Rak [this message]
2015-10-27 20:29 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562FD820.5050901@gameservers.com \
--to=brak@gameservers.com \
--cc=alexander.duyck@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.