From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, ncardwell@google.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, fw@strlen.de,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next v2 0/2] selftests/net: add packetdrill
Date: Thu, 5 Sep 2024 19:15:50 -0400 [thread overview]
Message-ID: <20240905231653.2427327-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Lay the groundwork to import into kselftests the over 150 packetdrill
TCP/IP conformance tests on github.com/google/packetdrill.
1/2: add kselftest infra for TEST_PROGS that need an interpreter
2/2: add the specific packetdrill tests
Both can go through net-next, I imagine. But let me know if the
core infra should go through linux-kselftest.
Willem de Bruijn (2):
selftests: support interpreted scripts with ksft_runner.sh
selftests/net: integrate packetdrill with ksft
tools/testing/selftests/Makefile | 5 +-
tools/testing/selftests/kselftest/runner.sh | 7 ++-
.../selftests/net/packetdrill/Makefile | 9 +++
.../testing/selftests/net/packetdrill/config | 5 ++
.../selftests/net/packetdrill/defaults.sh | 63 +++++++++++++++++++
.../selftests/net/packetdrill/ksft_runner.sh | 41 ++++++++++++
.../net/packetdrill/tcp_inq_client.pkt | 51 +++++++++++++++
.../net/packetdrill/tcp_inq_server.pkt | 51 +++++++++++++++
.../tcp_md5_md5-only-on-client-ack.pkt | 28 +++++++++
9 files changed, 256 insertions(+), 4 deletions(-)
create mode 100644 tools/testing/selftests/net/packetdrill/Makefile
create mode 100644 tools/testing/selftests/net/packetdrill/config
create mode 100755 tools/testing/selftests/net/packetdrill/defaults.sh
create mode 100755 tools/testing/selftests/net/packetdrill/ksft_runner.sh
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_inq_client.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_inq_server.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_md5_md5-only-on-client-ack.pkt
--
2.46.0.469.g59c65b2a67-goog
next reply other threads:[~2024-09-05 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 23:15 Willem de Bruijn [this message]
2024-09-05 23:15 ` [PATCH net-next v2 1/2] selftests: support interpreted scripts with ksft_runner.sh Willem de Bruijn
2024-09-05 23:15 ` [PATCH net-next v2 2/2] selftests/net: integrate packetdrill with ksft Willem de Bruijn
2024-09-06 11:43 ` Matthieu Baerts
2024-09-06 15:36 ` Willem de Bruijn
2024-09-06 16:26 ` Matthieu Baerts
2024-09-06 23:28 ` Willem de Bruijn
2024-09-07 0:04 ` Jakub Kicinski
2024-09-09 7:42 ` Matthieu Baerts
2024-09-09 13:15 ` Willem de Bruijn
2024-09-09 14:14 ` Matthieu Baerts
2024-09-09 17:21 ` [PATCH net-next v2 0/2] selftests/net: add packetdrill Jakub Kicinski
2024-09-10 17:45 ` Willem de Bruijn
2024-09-10 22:26 ` Jakub Kicinski
2024-09-10 0:40 ` 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=20240905231653.2427327-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--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