From: Simon Horman <horms@kernel.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net 4/4] selftests: vrf_route_leaking: add local ping test
Date: Thu, 27 Jun 2024 11:57:34 +0100 [thread overview]
Message-ID: <20240627105734.GF3104@kernel.org> (raw)
In-Reply-To: <20240624130859.953608-5-nicolas.dichtel@6wind.com>
On Mon, Jun 24, 2024 at 03:07:56PM +0200, Nicolas Dichtel wrote:
> The goal is to check that the source address selected by the kernel is
> routable when a leaking route is used.
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> ---
> .../selftests/net/vrf_route_leaking.sh | 38 ++++++++++++++++++-
> 1 file changed, 36 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/net/vrf_route_leaking.sh b/tools/testing/selftests/net/vrf_route_leaking.sh
> index 2da32f4c479b..6c59e0bbbde3 100755
> --- a/tools/testing/selftests/net/vrf_route_leaking.sh
> +++ b/tools/testing/selftests/net/vrf_route_leaking.sh
> @@ -533,6 +533,38 @@ ipv6_ping_frag_asym()
> ipv6_ping_frag asym
> }
>
> +ipv4_ping_local()
> +{
> + local ttype="$1"
> +
> + [ "x$ttype" = "x" ] && ttype="$DEFAULT_TTYPE"
Hi Nicolas,
I see this pattern already elsewhere in this file, but shellecheck flags that:
1. No arguments are passed to ipv4_ping_local
2. The condition can be more simply expressed as [ "$ttype" = "" ]
(my 2c worth would be [ -z "$ttype" ])
Nit picking aside, I'm genuinely curious about 1, is it actually the case?
> +
> + log_section "IPv4 ($ttype route): VRF ICMP local error route lookup ping"
> +
> + setup_"$ttype"
> +
> + check_connectivity || return
> +
> + run_cmd ip netns exec $r1 ip vrf exec blue ping -c1 -w1 ${H2_N2_IP}
> + log_test $? 0 "VRF ICMP local IPv4"
> +}
...
> @@ -594,12 +626,14 @@ do
> ipv4_traceroute|traceroute) ipv4_traceroute;;&
> ipv4_traceroute_asym|traceroute) ipv4_traceroute_asym;;&
> ipv4_ping_frag|ping) ipv4_ping_frag;;&
> + ipv4_ping_local|ping) ipv4_ping_local;;&
>
> ipv6_ping_ttl|ping) ipv6_ping_ttl;;&
> ipv6_ping_ttl_asym|ping) ipv6_ping_ttl_asym;;&
> ipv6_traceroute|traceroute) ipv6_traceroute;;&
> ipv6_traceroute_asym|traceroute) ipv6_traceroute_asym;;&
> ipv6_ping_frag|ping) ipv6_ping_frag;;&
> + ipv6_ping_local|ping) ipv6_ping_local;;&
>
> # setup namespaces and config, but do not run any tests
> setup_sym|setup) setup_sym; exit 0;;
> --
> 2.43.1
>
>
next prev parent reply other threads:[~2024-06-27 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:07 [PATCH net 0/4] vrf: fix source address selection with route leak Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 1/4] ipv4: " Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 2/4] ipv6: " Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 3/4] ipv6: take care of scope when choosing the src addr Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 4/4] selftests: vrf_route_leaking: add local ping test Nicolas Dichtel
2024-06-27 10:57 ` Simon Horman [this message]
2024-07-05 13:34 ` Nicolas Dichtel
2024-06-24 20:30 ` [PATCH net 0/4] vrf: fix source address selection with route leak Jakub Kicinski
2024-06-24 21:37 ` Nicolas Dichtel
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=20240627105734.GF3104@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.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).