From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>, memxor@gmail.com
Cc: puranjay@kernel.org, info@starlabs.sg, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Add load-acquire test for dst_reg == src_reg from ctx
Date: Wed, 05 Aug 2026 02:23:13 -0700 [thread overview]
Message-ID: <428d1069d408ec5ea597fd3ad610c4530f883953.camel@gmail.com> (raw)
In-Reply-To: <20260804201917.253491-2-daniel@iogearbox.net>
On Tue, 2026-08-04 at 22:19 +0200, Daniel Borkmann wrote:
> Add a verifier test that a load-acquire fetching into its own source
> register (dst_reg == src_reg) from a ctx pointer is rejected.
>
> # LDLIBS=-static PKG_CONFIG='pkg-config --static' ./vmtest.sh -- ./test_progs -t verifier_load_acquire
> [...]
> #614/1 verifier_load_acquire/load-acquire, 8-bit:OK
> #614/2 verifier_load_acquire/load-acquire, 8-bit @unpriv:OK
> #614/3 verifier_load_acquire/load-acquire, 16-bit:OK
> #614/4 verifier_load_acquire/load-acquire, 16-bit @unpriv:OK
> #614/5 verifier_load_acquire/load-acquire, 32-bit:OK
> #614/6 verifier_load_acquire/load-acquire, 32-bit @unpriv:OK
> #614/7 verifier_load_acquire/load-acquire, 64-bit:OK
> #614/8 verifier_load_acquire/load-acquire, 64-bit @unpriv:OK
> #614/9 verifier_load_acquire/load-acquire with uninitialized src_reg:OK
> #614/10 verifier_load_acquire/load-acquire with uninitialized src_reg @unpriv:OK
> #614/11 verifier_load_acquire/load-acquire with non-pointer src_reg:OK
> #614/12 verifier_load_acquire/load-acquire with non-pointer src_reg @unpriv:OK
> #614/13 verifier_load_acquire/misaligned load-acquire:OK
> #614/14 verifier_load_acquire/misaligned load-acquire @unpriv:OK
> #614/15 verifier_load_acquire/load-acquire from ctx pointer:OK
> #614/16 verifier_load_acquire/load-acquire from ctx pointer @unpriv:OK
> #614/17 verifier_load_acquire/load-acquire from ctx pointer, same dst and src register:OK
> #614/18 verifier_load_acquire/load-acquire from ctx pointer, same dst and src register @unpriv:OK
> #614/19 verifier_load_acquire/load-acquire with invalid register R15:OK
> #614/20 verifier_load_acquire/load-acquire with invalid register R15 @unpriv:OK
> #614/21 verifier_load_acquire/load-acquire from pkt pointer:OK
> #614/22 verifier_load_acquire/load-acquire from flow_keys pointer:OK
> #614/23 verifier_load_acquire/load-acquire from sock pointer:OK
> #614 verifier_load_acquire:OK
> Summary: 1/23 PASSED, 0 SKIPPED, 0 FAILED
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
...
next prev parent reply other threads:[~2026-08-05 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:19 [PATCH bpf-next 1/2] bpf: Check load-acquire src ptr type before the load Daniel Borkmann
2026-08-04 20:19 ` [PATCH bpf-next 2/2] selftests/bpf: Add load-acquire test for dst_reg == src_reg from ctx Daniel Borkmann
2026-08-05 9:23 ` Eduard Zingerman [this message]
2026-08-05 9:22 ` [PATCH bpf-next 1/2] bpf: Check load-acquire src ptr type before the load Eduard Zingerman
2026-08-05 10:10 ` 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=428d1069d408ec5ea597fd3ad610c4530f883953.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=info@starlabs.sg \
--cc=memxor@gmail.com \
--cc=puranjay@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