From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net 2/2] selftests: fib_nexthops: Add test case for ipv4 multi nexthops
Date: Sun, 14 Dec 2025 06:26:03 +0900 [thread overview]
Message-ID: <8cd00280-08a0-457d-a7c6-a88670595ce8@linux.dev> (raw)
In-Reply-To: <willemdebruijn.kernel.2568c56f18788@gmail.com>
On 13/12/2025 21:18, Willem de Bruijn wrote:
> Vadim Fedorenko wrote:
>> The test checks that with multi nexthops route the preferred route is the
>> one which matches source ip. In case when source ip is on loopback, it
>> checks that the routes are balanced.
>
> are balanced [across .. ]
Got it.
>
>>
>> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
>> ---
>> tools/testing/selftests/net/fib_nexthops.sh | 85 +++++++++++++++++++++
>> 1 file changed, 85 insertions(+)
>>
>> diff --git a/tools/testing/selftests/net/fib_nexthops.sh b/tools/testing/selftests/net/fib_nexthops.sh
>> index 2b0a90581e2f..9d6f57399a73 100755
>> --- a/tools/testing/selftests/net/fib_nexthops.sh
>> +++ b/tools/testing/selftests/net/fib_nexthops.sh
>> @@ -31,6 +31,7 @@ IPV4_TESTS="
>> ipv4_compat_mode
>> ipv4_fdb_grp_fcnal
>> ipv4_mpath_select
>> + ipv4_mpath_select_nogrp
>> ipv4_torture
>> ipv4_res_torture
>> "
>> @@ -375,6 +376,17 @@ check_large_res_grp()
>> log_test $? 0 "Dump large (x$buckets) nexthop buckets"
>> }
>>
>> +get_route_dev_src()
>> +{
>> + local pfx="$1"
>> + local src="$2"
>> + local out
>> +
>> + if out=$($IP -j route get "$pfx" from "$src" | jq -re ".[0].dev"); then
>> + echo "$out"
>> + fi
>> +}
>> +
>> get_route_dev()
>> {
>> local pfx="$1"
>> @@ -641,6 +653,79 @@ ipv4_fdb_grp_fcnal()
>> $IP link del dev vx10
>> }
>>
>> +ipv4_mpath_select_nogrp()
>
> There is more going on than just not using the group feature.
>
> Would it make sense to split this into two test patches, a base test
> and a follow-on that extends with the loopback special case?
Sounds reasonable, I'll split it in v2
>
>> +{
>> + local rc dev match h addr
>> +
>> + echo
>> + echo "IPv4 multipath selection no group"
>> + echo "------------------------"
>> + if [ ! -x "$(command -v jq)" ]; then
>> + echo "SKIP: Could not run test; need jq tool"
>> + return $ksft_skip
>> + fi
>> +
>> + IP="ip -netns $peer"
>> + # Use status of existing neighbor entry when determining nexthop for
>> + # multipath routes.
>> + local -A gws
>> + gws=([veth2]=172.16.1.1 [veth4]=172.16.2.1)
>> + local -A other_dev
>> + other_dev=([veth2]=veth4 [veth4]=veth2)
>> + local -A local_ips
>> + local_ips=([veth2]=172.16.1.2 [veth4]=172.16.2.2 [veth5]=172.16.100.1)
>
> Why do both loopback and veth5 exist with the same local ip. Can this just be lo?
Ah, yeah, looks like a leftover from previous version, thanks for
catching!
>> + local -A route_devs
>> + route_devs=([veth2]=0 [veth4]=0)
>> +
>> + run_cmd "$IP address add 172.16.100.1/32 dev lo"
>> + run_cmd "$IP ro add 172.16.102.0/24 nexthop via ${gws['veth2']} dev veth2 nexthop via ${gws['veth4']} dev veth4"
>> + rc=0
>> + for dev in veth2 veth4; do
>> + match=0
>> + from_ip="${local_ips[$dev]}"
>> + for h in {1..254}; do
>> + addr="172.16.102.$h"
>> + if [ "$(get_route_dev_src "$addr" "$from_ip")" = "$dev" ]; then
>> + match=1
>> + break
>> + fi
>> + done
>> + if (( match == 0 )); then
>> + echo "SKIP: Did not find a route using device $dev"
>> + return $ksft_skip
>> + fi
>> + run_cmd "$IP neigh add ${gws[$dev]} dev $dev nud failed"
>> + if ! check_route_dev "$addr" "${other_dev[$dev]}"; then
>> + rc=1
>> + break
>> + fi
>> + run_cmd "$IP neigh del ${gws[$dev]} dev $dev"
>> + done
>> +
>> + log_test $rc 0 "Use valid neighbor during multipath selection"
>> +
>> + from_ip="${local_ips["veth5"]}"
>> + for h in {1..254}; do
>> + addr="172.16.102.$h"
>> + route_dev=$(get_route_dev_src "$addr" "$from_ip")
>> + route_devs[$route_dev]=1
>> + done
>> + for dev in veth2 veth4; do
>> + if [ ${route_devs[$dev]} -eq 0 ]; then
>> + rc=1
>> + break;
>> + fi
>> + done
>> +
>> + log_test $rc 0 "Use both neighbors during multipath selection"
>> +
>> + run_cmd "$IP neigh add 172.16.1.2 dev veth1 nud incomplete"
>> + run_cmd "$IP neigh add 172.16.2.2 dev veth3 nud incomplete"
>> + run_cmd "$IP route get 172.16.101.1"
>> + # if we did not crash, success
>> + log_test $rc 0 "Multipath selection with no valid neighbor"
>> +}
>> +
>> ipv4_mpath_select()
>> {
>> local rc dev match h addr
>> --
>> 2.47.3
>>
>
>
next prev parent reply other threads:[~2025-12-13 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 13:58 [PATCH net 1/2] net: fib: restore ECMP balance from loopback Vadim Fedorenko
2025-12-13 13:58 ` [PATCH net 2/2] selftests: fib_nexthops: Add test case for ipv4 multi nexthops Vadim Fedorenko
2025-12-13 21:18 ` Willem de Bruijn
2025-12-13 21:26 ` Vadim Fedorenko [this message]
2025-12-13 22:02 ` David Ahern
2025-12-15 6:59 ` Ido Schimmel
2025-12-15 16:13 ` David Ahern
2025-12-15 19:01 ` Vadim Fedorenko
2025-12-13 20:54 ` [PATCH net 1/2] net: fib: restore ECMP balance from loopback Willem de Bruijn
2025-12-13 21:22 ` Vadim Fedorenko
2025-12-15 21:45 ` Willem de Bruijn
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=8cd00280-08a0-457d-a7c6-a88670595ce8@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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).