From: Michal Kubecek <mkubecek@suse.cz>
To: netdev@vger.kernel.org
Cc: Benjamin Poirier <bpoirier@cumulusnetworks.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH net 1/2] ipv6: Fix route replacement with dev-only route
Date: Wed, 12 Feb 2020 22:57:22 +0100 [thread overview]
Message-ID: <20200212215722.GB21997@unicorn.suse.cz> (raw)
In-Reply-To: <20200212014107.110066-1-bpoirier@cumulusnetworks.com>
On Wed, Feb 12, 2020 at 10:41:06AM +0900, Benjamin Poirier wrote:
> After commit 27596472473a ("ipv6: fix ECMP route replacement") it is no
> longer possible to replace an ECMP-able route by a non ECMP-able route.
> For example,
> ip route add 2001:db8::1/128 via fe80::1 dev dummy0
> ip route replace 2001:db8::1/128 dev dummy0
> does not work as expected.
>
> Tweak the replacement logic so that point 3 in the log of the above commit
> becomes:
> 3. If the new route is not ECMP-able, and no matching non-ECMP-able route
> exists, replace matching ECMP-able route (if any) or add the new route.
>
> We can now summarize the entire replace semantics to:
> When doing a replace, prefer replacing a matching route of the same
> "ECMP-able-ness" as the replace argument. If there is no such candidate,
> fallback to the first route found.
>
> Fixes: 27596472473a ("ipv6: fix ECMP route replacement")
> Signed-off-by: Benjamin Poirier <bpoirier@cumulusnetworks.com>
Reviewed-by: Michal Kubecek <mkubecek@suse.cz>
> ---
> net/ipv6/ip6_fib.c | 7 ++++---
> tools/testing/selftests/net/fib_tests.sh | 6 ++++++
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv6/ip6_fib.c b/net/ipv6/ip6_fib.c
> index 58fbde244381..72abf892302f 100644
> --- a/net/ipv6/ip6_fib.c
> +++ b/net/ipv6/ip6_fib.c
> @@ -1102,8 +1102,7 @@ static int fib6_add_rt2node(struct fib6_node *fn, struct fib6_info *rt,
> found++;
> break;
> }
> - if (rt_can_ecmp)
> - fallback_ins = fallback_ins ?: ins;
> + fallback_ins = fallback_ins ?: ins;
> goto next_iter;
> }
>
> @@ -1146,7 +1145,9 @@ static int fib6_add_rt2node(struct fib6_node *fn, struct fib6_info *rt,
> }
>
> if (fallback_ins && !found) {
> - /* No ECMP-able route found, replace first non-ECMP one */
> + /* No matching route with same ecmp-able-ness found, replace
> + * first matching route
> + */
> ins = fallback_ins;
> iter = rcu_dereference_protected(*ins,
> lockdep_is_held(&rt->fib6_table->tb6_lock));
> diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
> index 6dd403103800..60273f1bc7d9 100755
> --- a/tools/testing/selftests/net/fib_tests.sh
> +++ b/tools/testing/selftests/net/fib_tests.sh
> @@ -910,6 +910,12 @@ ipv6_rt_replace_mpath()
> check_route6 "2001:db8:104::/64 via 2001:db8:101::3 dev veth1 metric 1024"
> log_test $? 0 "Multipath with single path via multipath attribute"
>
> + # multipath with dev-only
> + add_initial_route6 "nexthop via 2001:db8:101::2 nexthop via 2001:db8:103::2"
> + run_cmd "$IP -6 ro replace 2001:db8:104::/64 dev veth1"
> + check_route6 "2001:db8:104::/64 dev veth1 metric 1024"
> + log_test $? 0 "Multipath with dev-only"
> +
> # route replace fails - invalid nexthop 1
> add_initial_route6 "nexthop via 2001:db8:101::2 nexthop via 2001:db8:103::2"
> run_cmd "$IP -6 ro replace 2001:db8:104::/64 nexthop via 2001:db8:111::3 nexthop via 2001:db8:103::3"
> --
> 2.25.0
>
next prev parent reply other threads:[~2020-02-12 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 1:41 [PATCH net 1/2] ipv6: Fix route replacement with dev-only route Benjamin Poirier
2020-02-12 1:41 ` [PATCH net 2/2] ipv6: Fix nlmsg_flags when splitting a multipath route Benjamin Poirier
2020-02-12 21:58 ` Michal Kubecek
2020-02-15 17:58 ` David Ahern
2020-02-17 2:35 ` David Miller
2020-02-12 21:57 ` Michal Kubecek [this message]
2020-02-15 18:00 ` [PATCH net 1/2] ipv6: Fix route replacement with dev-only route David Ahern
2020-02-17 3:12 ` Benjamin Poirier
2020-02-20 3:20 ` Cong Wang
2020-02-17 2:35 ` David Miller
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=20200212215722.GB21997@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=bpoirier@cumulusnetworks.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).