From: David Ahern <dsahern@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, willemb@google.com
Subject: Re: [PATCH net-next v2 2/2] selftests: fib_tests: Add test cases for route lookup with oif
Date: Mon, 1 Jun 2026 20:53:17 -0600 [thread overview]
Message-ID: <3dff2e67-5d21-4059-bb01-dc601b75b733@kernel.org> (raw)
In-Reply-To: <20260601065300.267960-3-idosch@nvidia.com>
On 6/1/26 12:53 AM, Ido Schimmel wrote:
> Test that both address families respect the oif parameter when a
> matching multipath route is found, regardless of the presence of a
> source address.
>
> Output without "ipv6: Honor oif when choosing nexthop for locally
> generated traffic":
>
> # ./fib_tests.sh -t "ipv4_mpath_oif ipv4_mpath_oif_vrf ipv6_mpath_oif ipv6_mpath_oif_vrf"
>
> IPv4 multipath oif test
> TEST: IPv4 multipath via first nexthop [ OK ]
> TEST: IPv4 multipath via second nexthop [ OK ]
> TEST: IPv4 multipath via first nexthop with source address [ OK ]
> TEST: IPv4 multipath via second nexthop with source address [ OK ]
>
> IPv4 multipath oif with VRF test
> TEST: IPv4 multipath via first nexthop [ OK ]
> TEST: IPv4 multipath via second nexthop [ OK ]
> TEST: IPv4 multipath via first nexthop with source address [ OK ]
> TEST: IPv4 multipath via second nexthop with source address [ OK ]
>
> IPv6 multipath oif test
> TEST: IPv6 multipath via first nexthop [ OK ]
> TEST: IPv6 multipath via second nexthop [ OK ]
> TEST: IPv6 multipath via first nexthop with source address [FAIL]
> TEST: IPv6 multipath via second nexthop with source address [FAIL]
>
> IPv6 multipath oif with VRF test
> TEST: IPv6 multipath via first nexthop [ OK ]
> TEST: IPv6 multipath via second nexthop [ OK ]
> TEST: IPv6 multipath via first nexthop with source address [FAIL]
> TEST: IPv6 multipath via second nexthop with source address [FAIL]
>
> Tests passed: 12
> Tests failed: 4
>
> Output with "ipv6: Honor oif when choosing nexthop for locally generated
> traffic":
>
> # ./fib_tests.sh -t "ipv4_mpath_oif ipv4_mpath_oif_vrf ipv6_mpath_oif ipv6_mpath_oif_vrf"
>
> IPv4 multipath oif test
> TEST: IPv4 multipath via first nexthop [ OK ]
> TEST: IPv4 multipath via second nexthop [ OK ]
> TEST: IPv4 multipath via first nexthop with source address [ OK ]
> TEST: IPv4 multipath via second nexthop with source address [ OK ]
>
> IPv4 multipath oif with VRF test
> TEST: IPv4 multipath via first nexthop [ OK ]
> TEST: IPv4 multipath via second nexthop [ OK ]
> TEST: IPv4 multipath via first nexthop with source address [ OK ]
> TEST: IPv4 multipath via second nexthop with source address [ OK ]
>
> IPv6 multipath oif test
> TEST: IPv6 multipath via first nexthop [ OK ]
> TEST: IPv6 multipath via second nexthop [ OK ]
> TEST: IPv6 multipath via first nexthop with source address [ OK ]
> TEST: IPv6 multipath via second nexthop with source address [ OK ]
>
> IPv6 multipath oif with VRF test
> TEST: IPv6 multipath via first nexthop [ OK ]
> TEST: IPv6 multipath via second nexthop [ OK ]
> TEST: IPv6 multipath via first nexthop with source address [ OK ]
> TEST: IPv6 multipath via second nexthop with source address [ OK ]
>
> Tests passed: 16
> Tests failed: 0
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> tools/testing/selftests/net/fib_tests.sh | 183 ++++++++++++++++++++++-
> 1 file changed, 182 insertions(+), 1 deletion(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
prev parent reply other threads:[~2026-06-02 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:52 [PATCH net-next v2 0/2] ipv6: Honor oif when choosing nexthop for locally generated traffic Ido Schimmel
2026-06-01 6:52 ` [PATCH net-next v2 1/2] " Ido Schimmel
2026-06-02 2:51 ` David Ahern
2026-06-01 6:53 ` [PATCH net-next v2 2/2] selftests: fib_tests: Add test cases for route lookup with oif Ido Schimmel
2026-06-02 2:53 ` David Ahern [this message]
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=3dff2e67-5d21-4059-bb01-dc601b75b733@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--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=willemb@google.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