[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190624.102029.1787909800092048267.davem@davemloft.net>
Date: Mon, 24 Jun 2019 10:20:29 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: sbrivio@...hat.com
Cc: dsahern@...il.com, jishi@...hat.com, weiwan@...gle.com,
kafai@...com, edumazet@...gle.com,
matti.vaittinen@...rohmeurope.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v7 00/11] Fix listing (IPv4, IPv6) and
flushing (IPv6) of cached route exceptions
From: Stefano Brivio <sbrivio@...hat.com>
Date: Fri, 21 Jun 2019 17:45:19 +0200
> For IPv6 cached routes, the commands 'ip -6 route list cache' and
> 'ip -6 route flush cache' don't work at all after route exceptions have
> been moved to a separate hash table in commit 2b760fcf5cfb ("ipv6: hook
> up exception table to store dst cache").
>
> For IPv4 cached routes, the command 'ip route list cache' has also
> stopped working in kernel 3.5 after commit 4895c771c7f0 ("ipv4: Add FIB
> nexthop exceptions.") introduced storage for route exceptions as a
> separate entity.
>
> Fix this by allowing userspace to clearly request cached routes with
> the RTM_F_CLONED flag used as a filter (in conjuction with strict
> checking) and by retrieving and dumping cached routes if requested.
>
> If strict checking is not requested (iproute2 < 5.0.0), we don't have a
> way to consistently filter results on other selectors (e.g. on tables),
> so skip filtering entirely and dump both regular routes and exceptions.
>
> For IPv4, cache flushing uses a completely different mechanism, so it
> wasn't affected. Listing of exception routes (modified routes pre-3.5) was
> tested against these versions of kernel and iproute2:
...
Series applied, thanks.
Powered by blists - more mailing lists