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/[email protected]/
 - Rebase onto the latest net-next tree to resolve merge conflicts.

v3: https://lore.kernel.org/netdev/[email protected]/
 - Re-send the patch series becasue Patchwork don't update them.

v2: https://lore.kernel.org/netdev/[email protected]/
 - 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/[email protected]/

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


Reply via email to