From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next] selftests/net: packetdrill: Support single protocol test.
Date: Wed, 20 Aug 2025 07:29:38 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.1deb495a9cf2b@gmail.com> (raw)
In-Reply-To: <20250819231527.1427361-1-kuniyu@google.com>
Kuniyuki Iwashima wrote:
> Currently, we cannot write IPv4 or IPv6 specific packetdrill tests
> as ksft_runner.sh runs each .pkt file for both protocols.
>
> Let's support single protocol test by checking --ip_version in the
> .pkt file.
>
> Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
> ---
> .../selftests/net/packetdrill/ksft_runner.sh | 47 +++++++++++--------
> 1 file changed, 28 insertions(+), 19 deletions(-)
>
> diff --git a/tools/testing/selftests/net/packetdrill/ksft_runner.sh b/tools/testing/selftests/net/packetdrill/ksft_runner.sh
> index a7e790af38ff..0ae6eeeb1a8e 100755
> --- a/tools/testing/selftests/net/packetdrill/ksft_runner.sh
> +++ b/tools/testing/selftests/net/packetdrill/ksft_runner.sh
> @@ -3,21 +3,22 @@
>
> source "$(dirname $(realpath $0))/../../kselftest/ktap_helpers.sh"
>
> -readonly ipv4_args=('--ip_version=ipv4 '
> - '--local_ip=192.168.0.1 '
> - '--gateway_ip=192.168.0.1 '
> - '--netmask_ip=255.255.0.0 '
> - '--remote_ip=192.0.2.1 '
> - '-D CMSG_LEVEL_IP=SOL_IP '
> - '-D CMSG_TYPE_RECVERR=IP_RECVERR ')
> -
> -readonly ipv6_args=('--ip_version=ipv6 '
> - '--mtu=1520 '
> - '--local_ip=fd3d:0a0b:17d6::1 '
> - '--gateway_ip=fd3d:0a0b:17d6:8888::1 '
> - '--remote_ip=fd3d:fa7b:d17d::1 '
> - '-D CMSG_LEVEL_IP=SOL_IPV6 '
> - '-D CMSG_TYPE_RECVERR=IPV6_RECVERR ')
> +declare -A ip_args=(
> + [ipv4]="--ip_version=ipv4
> + --local_ip=192.168.0.1
> + --gateway_ip=192.168.0.1
> + --netmask_ip=255.255.0.0
> + --remote_ip=192.0.2.1
> + -D CMSG_LEVEL_IP=SOL_IP
> + -D CMSG_TYPE_RECVERR=IP_RECVERR"
> + [ipv6]="--ip_version=ipv6
> + --mtu=1520
> + --local_ip=fd3d:0a0b:17d6::1
> + --gateway_ip=fd3d:0a0b:17d6:8888::1
> + --remote_ip=fd3d:fa7b:d17d::1
> + -D CMSG_LEVEL_IP=SOL_IPV6
> + -D CMSG_TYPE_RECVERR=IPV6_RECVERR"
> +)
>
> if [ $# -ne 1 ]; then
> ktap_exit_fail_msg "usage: $0 <script>"
> @@ -38,12 +39,20 @@ if [[ -n "${KSFT_MACHINE_SLOW}" ]]; then
> failfunc=ktap_test_xfail
> fi
>
> +ip_versions=$(grep -E '^--ip_version=' $script | cut -d '=' -f 2)
> +if [[ -z $ip_versions ]]; then
> + ip_versions="ipv4 ipv6"
> +elif [[ ! "$ip_versions" =~ ^ipv[46]$ ]]; then
> + ktap_exit_fail_msg "Too many or unsupported --ip_version: $ip_versions"
> + exit "$KSFT_FAIL"
> +fi
> +
> ktap_print_header
> ktap_set_plan 2
>
> -unshare -n packetdrill ${ipv4_args[@]} ${optargs[@]} $script > /dev/null \
> - && ktap_test_pass "ipv4" || $failfunc "ipv4"
> -unshare -n packetdrill ${ipv6_args[@]} ${optargs[@]} $script > /dev/null \
> - && ktap_test_pass "ipv6" || $failfunc "ipv6"
> +for ip_version in $ip_versions; do
> + unshare -n packetdrill ${ip_args[$ip_version]} ${optargs[@]} $script > /dev/null \
> + && ktap_test_pass $ip_version || $failfunc $ip_version
minor if respinning: indentation of 4 spaces instead of tab.
next prev parent reply other threads:[~2025-08-20 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 23:14 [PATCH v1 net-next] selftests/net: packetdrill: Support single protocol test Kuniyuki Iwashima
2025-08-20 11:29 ` Willem de Bruijn [this message]
2025-08-21 2:50 ` patchwork-bot+netdevbpf
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=willemdebruijn.kernel.1deb495a9cf2b@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.