netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: [RFC PATCH net-next v2 0/8] selftest: Extend tun/virtio coverage for GSO over UDP tunnel
Date: Tue, 30 Dec 2025 15:59:04 +0800	[thread overview]
Message-ID: <cover.1767074545.git.xudu@redhat.com> (raw)

The primary goal is to add test validation for GSO when operating over
UDP tunnels, a scenario which is not currently covered.

The design strategy is to extend the existing tun/tap 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.

---
v1 -> v2:
 - 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 (8):
  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: tap: Refactor tap test 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/tap.c            | 287 +-----
 tools/testing/selftests/net/tun.c            | 917 ++++++++++++++++++-
 tools/testing/selftests/net/tuntap_helpers.h | 608 ++++++++++++
 3 files changed, 1530 insertions(+), 282 deletions(-)
 create mode 100644 tools/testing/selftests/net/tuntap_helpers.h


base-commit: 7b8e9264f55a9c320f398e337d215e68cca50131
-- 
2.49.0


             reply	other threads:[~2025-12-30  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  7:59 Xu Du [this message]
2025-12-30  7:59 ` [RFC PATCH net-next v2 1/8] selftest: tun: Format tun.c existing code Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 2/8] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 3/8] selftest: tun: Refactor tun_delete to use tuntap_helpers Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 4/8] selftest: tap: Refactor tap test " Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 5/8] selftest: tun: Add helpers for GSO over UDP tunnel Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 6/8] selftest: tun: Add test for sending gso packet into tun Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 7/8] selftest: tun: Add test for receiving gso packet from tun Xu Du
2025-12-30  7:59 ` [RFC PATCH net-next v2 8/8] 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.1767074545.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=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 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).