selftests: drv-net: run XDP tests with both IP versions
Status from this message: This series was applied to netdev/net-next.git (main)
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | selftests: drv-net: allow switching env IP versiontools/ | +20 | 0 replies | Applied |
| 2/2 | selftests: drv-net: xdp: run with both IP versionstools/ | +77 | 0 replies | Applied |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Carolina Jubran | Dragos Tatulea |
|---|---|---|
| 1/2 | R-b | R-b |
| 2/2 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH net-next 0/2] selftests: drv-net: run XDP tests with both IP versions
The driver selftest environment picks a single address family for tests which use the generic address fields. When both IPv4 and IPv6 are available it prefers IPv6, which can leave IPv4 paths untested and hide IPv4-only bugs.
This happened recently in the XDP selftest, where an IPv4 checksum bug was missed when IPv6 was also configured. XDP traffic handling has IP-version-specific code paths, and the follow-up discussion concluded that the XDP tests should run against both IP versions [1].
This series changes NetDrvEpEnv from exposing only the initially selected address family to allowing tests to switch the generic address fields between IP versions. xdp.py uses this to run the XDP traffic cases over both IPv4 and IPv6. Test variants whose required IP version is not configured are skipped.
[1] https://lore.kernel.org/[email protected]/
Nimrod Oren (2):
selftests: drv-net: allow switching env IP version
selftests: drv-net: xdp: run with both IP versions
.../selftests/drivers/net/lib/py/env.py | 27 ++++-- tools/testing/selftests/drivers/net/xdp.py | 94 +++++++++++++++---- 2 files changed, 97 insertions(+), 24 deletions(-)
Signature · 1 line
2.45.0