[PATCH net-next] selftests: drv-net: xdp: make sure we're actually testing native XDP

[PATCH net-next] selftests: drv-net: xdp: make sure we're actually testing native XDP

[Jakub Kicinski]

Kernel tries to be helpful and attach the XDP program in generic
mode if the driver has no BPF ndo at all. Since the xdp.py tests
all have "native" in their names this can be quite confusing.
Force native / "drv" attachment. Note that netdevsim re-uses
the generic handler as its "native" handler, so we'll maintain
the test coverage of the generic mode that way. No need to test
both explicitly, I reckon.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
 tools/testing/selftests/drivers/net/xdp.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/drivers/net/xdp.py b/tools/testing/selftests/drivers/net/xdp.py
index 35e9495cd506..08fea4230759 100755
--- a/tools/testing/selftests/drivers/net/xdp.py
+++ b/tools/testing/selftests/drivers/net/xdp.py
@@ -112,10 +112,10 @@ from lib.py import ip, bpftool, defer
     defer(ip, f"link set dev {cfg.remote_ifname} mtu 1500", host=cfg.remote)
 
     cmd(
-    f"ip link set dev {cfg.ifname} mtu {bpf_info.mtu} xdp obj {abs_path} sec {bpf_info.xdp_sec}",
+    f"ip link set dev {cfg.ifname} mtu {bpf_info.mtu} xdpdrv obj {abs_path} sec {bpf_info.xdp_sec}",
     shell=True
     )
-    defer(ip, f"link set dev {cfg.ifname} mtu 1500 xdp off")
+    defer(ip, f"link set dev {cfg.ifname} mtu 1500 xdpdrv off")
 
     xdp_info = ip(f"-d link show dev {cfg.ifname}", json=True)[0]
     prog_info["id"] = xdp_info["xdp"]["prog"]["id"]
-- 
2.50.1

Re: [PATCH net-next] selftests: drv-net: xdp: make sure we're actually testing native XDP

[patchwork-bot+netdevbpf]

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 22 Aug 2025 12:56:45 -0700 you wrote:
> Kernel tries to be helpful and attach the XDP program in generic
> mode if the driver has no BPF ndo at all. Since the xdp.py tests
> all have "native" in their names this can be quite confusing.
> Force native / "drv" attachment. Note that netdevsim re-uses
> the generic handler as its "native" handler, so we'll maintain
> the test coverage of the generic mode that way. No need to test
> both explicitly, I reckon.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: drv-net: xdp: make sure we're actually testing native XDP
    https://git.kernel.org/netdev/net-next/c/992e9f53a0db

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html