From: Jakub Kicinski <kuba@kernel.org>
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
shuah@kernel.org, horms@kernel.org, cratiu@nvidia.com,
noren@nvidia.com, cjubran@nvidia.com, mbloch@nvidia.com,
jdamato@fastly.com, gal@nvidia.com, sdf@fomichev.me,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next V2 0/5] selftests: drv-net: Test XDP native support
Date: Fri, 11 Jul 2025 06:39:17 -0700 [thread overview]
Message-ID: <20250711063917.7aad27f7@kernel.org> (raw)
In-Reply-To: <20250710184351.63797-1-mohsin.bashr@gmail.com>
On Thu, 10 Jul 2025 11:43:46 -0700 Mohsin Bashir wrote:
> This patch series add tests to validate XDP native support for PASS,
> DROP, ABORT, and TX actions, as well as headroom and tailroom adjustment.
> For adjustment tests, validate support for both the extension and
> shrinking cases across various packet sizes and offset values.
The program does not load in the CI :(
509: (15) if r1 == 0x0 goto pc+142 ; frame1: R1=scalar(smin=umin=umin32=1,smax=umax=0xffffffff,var_off=(0x0; 0xffffffff))
510: (25) if r1 > 0x100 goto pc+141 ; frame1: R1=scalar(smin=umin=smin32=umin32=1,smax=umax=smax32=umax32=256,var_off=(0x0; 0x1ff))
511: (bf) r3 = r10 ; frame1: R3_w=fp0 R10=fp0\n; if (bpf_xdp_load_bytes(ctx, 0, tmp_buff, hdr_len) < 0) @ xdp_native.bpf.c:377
512: (07) r3 += -256 ; frame1: R3_w=fp-256
513: (bf) r1 = r7 ; frame1: R1_w=ctx() R7=ctx()
514: (b7) r2 = 0 ; frame1: R2_w=0
515: (bf) r4 = r8 ; frame1: R4_w=scalar(id=3) R8=scalar(id=3)
516: (7b) *(u64 *)(r10 -280) = r5 ; frame1: R5=32 R10=fp0 fp-280_w=32
517: (85) call bpf_xdp_load_bytes#189
R4 min value is negative, either use unsigned or 'var &= const'
processed 262 insns (limit 1000000) max_states_per_insn 1 total_states 26 peak_states 26 mark_read 7
-- END PROG LOAD LOG
I suppose it may be due to compiler version:
$ clang --version
clang version 15.0.7 (AWS 15.0.7-3.amzn2023.0.4)
LMK if you need more info / can't repro, but I think the suggestion
makes sense?
next prev parent reply other threads:[~2025-07-11 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 18:43 [PATCH net-next V2 0/5] selftests: drv-net: Test XDP native support Mohsin Bashir
2025-07-10 18:43 ` [PATCH net-next 1/5] selftests: drv-net: Add bpftool util Mohsin Bashir
2025-07-11 17:10 ` Jakub Kicinski
2025-07-10 18:43 ` [PATCH net-next 2/5] selftests: drv-net: Test XDP_PASS/DROP support Mohsin Bashir
2025-07-11 13:41 ` Jakub Kicinski
2025-07-10 18:43 ` [PATCH net-next 3/5] selftests: drv-net: Test XDP_TX support Mohsin Bashir
2025-07-10 18:43 ` [PATCH net-next 4/5] selftests: drv-net: Test tail-adjustment support Mohsin Bashir
2025-07-10 18:43 ` [PATCH net-next 5/5] selftests: drv-net: Test head-adjustment support Mohsin Bashir
2025-07-11 13:39 ` Jakub Kicinski [this message]
2025-07-11 17:29 ` [PATCH net-next V2 0/5] selftests: drv-net: Test XDP native support Mohsin Bashir
2025-07-11 17:50 ` patchwork-bot+netdevbpf
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=20250711063917.7aad27f7@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--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).