From: Xu Du <xudu@redhat.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v5 0/7] selftest: Extend tun/virtio coverage for GSO over UDP tunnel
Date: Mon, 19 Jan 2026 13:39:57 +0800 [thread overview]
Message-ID: <cover.1768800198.git.xudu@redhat.com> (raw)
The design strategy is to extend the existing tun testing infrastructure
to support this new use-case, rather than introducing a new or parallel framework.
This allows for better integration and re-use of existing test logic.
---
v4 -> v5:
- Refactor the rtnetlink utilities to use YNL.
- Use Geneve tunnel instead of VXLAN tunnel.
- Revert tap refactor as YNL lacks macvtap support.
v4: https://lore.kernel.org/netdev/cover.1767597114.git.xudu@redhat.com/
- Rebase onto the latest net-next tree to resolve merge conflicts.
v3: https://lore.kernel.org/netdev/cover.1767580224.git.xudu@redhat.com/
- Re-send the patch series becasue Patchwork don't update them.
v2: https://lore.kernel.org/netdev/cover.1767074545.git.xudu@redhat.com/
- Addresse sporadic failures due to too early send.
- Refactor environment address assign helper function.
- Fix incorrect argument passing in build packet functions.
v1: https://lore.kernel.org/netdev/cover.1763345426.git.xudu@redhat.com/
Xu Du (7):
selftest: tun: Format tun.c existing code
selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing
selftest: tun: Refactor tun_delete to use tuntap_helpers
selftest: tun: Add helpers for GSO over UDP tunnel
selftest: tun: Add test for sending gso packet into tun
selftest: tun: Add test for receiving gso packet from tun
selftest: tun: Add test data for success and failure paths
tools/testing/selftests/net/Makefile | 7 +-
tools/testing/selftests/net/tun.c | 898 ++++++++++++++++++-
tools/testing/selftests/net/tuntap_helpers.h | 391 ++++++++
3 files changed, 1257 insertions(+), 39 deletions(-)
create mode 100644 tools/testing/selftests/net/tuntap_helpers.h
base-commit: c65182ef9df6bb96fd85b56a2bcdd18d64c4d3b5
--
2.49.0
next reply other threads:[~2026-01-19 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 5:39 Xu Du [this message]
2026-01-19 5:39 ` [PATCH net-next v5 1/7] selftest: tun: Format tun.c existing code Xu Du
2026-01-19 5:39 ` [PATCH net-next v5 2/7] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing Xu Du
2026-01-19 5:40 ` [PATCH net-next v5 3/7] selftest: tun: Refactor tun_delete to use tuntap_helpers Xu Du
2026-01-19 17:09 ` Jakub Kicinski
2026-01-20 1:32 ` Xu Du
2026-01-19 5:40 ` [PATCH net-next v5 4/7] selftest: tun: Add helpers for GSO over UDP tunnel Xu Du
2026-01-19 5:40 ` [PATCH net-next v5 5/7] selftest: tun: Add test for sending gso packet into tun Xu Du
2026-01-19 5:40 ` [PATCH net-next v5 6/7] selftest: tun: Add test for receiving gso packet from tun Xu Du
2026-01-19 5:40 ` [PATCH net-next v5 7/7] selftest: tun: Add test data for success and failure paths Xu Du
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=cover.1768800198.git.xudu@redhat.com \
--to=xudu@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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.