BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: memxor@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 5/6] selftests/bpf: Add tests for pointer type merge at a shared load
Date: Sun, 16 Aug 2026 15:24:24 -0700	[thread overview]
Message-ID: <99df26bd743e221a9b2d260546d30d73e5b80405.camel@gmail.com> (raw)
In-Reply-To: <20260814215301.709827-5-daniel@iogearbox.net>

On Fri, 2026-08-14 at 23:52 +0200, Daniel Borkmann wrote:
> Cover the ways in which the type recorded for a shared load used to lose
> the BPF_PROBE_MEM rewrite which would then trigger a NULL deref if not
> handled properly.
> 
>   # LDLIBS=-static PKG_CONFIG='pkg-config --static' ./vmtest.sh -- ./test_progs -t mem_rdonly_untrusted
>   [...]
>   #238/1   mem_rdonly_untrusted/btf_id_to_ptr_mem:OK
>   #238/2   mem_rdonly_untrusted/ldx_is_ok_bad_addr:OK
>   #238/3   mem_rdonly_untrusted/ldx_is_ok_good_addr:OK
>   #238/4   mem_rdonly_untrusted/offset_not_tracked:OK
>   #238/5   mem_rdonly_untrusted/stx_not_ok:OK
>   #238/6   mem_rdonly_untrusted/atomic_not_ok:OK
>   #238/7   mem_rdonly_untrusted/atomic_rmw_not_ok:OK
>   #238/8   mem_rdonly_untrusted/kfunc_param_not_ok:OK
>   #238/9   mem_rdonly_untrusted/mixed_mem_type:OK
>   #238/10  mem_rdonly_untrusted/mixed_mem_untrusted_btf_id_type:OK
>   #238/11  mem_rdonly_untrusted/mixed_mem_btf_id_type:OK
>   #238/12  mem_rdonly_untrusted/mixed_rdonly_mem_btf_id_type:OK
>   #238/13  mem_rdonly_untrusted/mixed_mem_mem_type:OK
>   #238/14  mem_rdonly_untrusted/mixed_map_value_mem_type:OK
>   #238/15  mem_rdonly_untrusted/mixed_stack_mem_type:OK
>   #238/16  mem_rdonly_untrusted/diff_size_access:OK
>   #238/17  mem_rdonly_untrusted/misaligned_access:OK
>   #238/18  mem_rdonly_untrusted/null_check:OK
>   #238/19  mem_rdonly_untrusted/ldx_is_ok_commuted_addr:OK
>   #238/20  mem_rdonly_untrusted/helper_param_not_ok:OK
>   #238     mem_rdonly_untrusted:OK
>   Summary: 1/20 PASSED, 0 SKIPPED, 0/0 FAILED
> 
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---

Acked-by: Eduard Zingerman <eddyz87@gmail.com>

...

  parent reply	other threads:[~2026-08-16 22:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 21:52 [PATCH bpf-next v2 1/6] bpf: Keep fault protection when merging pointer types Daniel Borkmann
2026-08-14 21:52 ` [PATCH bpf-next v2 2/6] bpf: Treat a fault prone PTR_TO_MEM as a pointer type mismatch Daniel Borkmann
2026-08-16 19:44   ` Eduard Zingerman
2026-08-14 21:52 ` [PATCH bpf-next v2 3/6] bpf: Reject a store through a fault prone pointer Daniel Borkmann
2026-08-14 22:40   ` bot+bpf-ci
2026-08-14 23:26     ` Daniel Borkmann
2026-08-16 19:54   ` Eduard Zingerman
2026-08-16 20:02     ` Eduard Zingerman
2026-08-14 21:52 ` [PATCH bpf-next v2 4/6] bpf: Rewrite any fault prone load out of a mem or btf_id pointer Daniel Borkmann
2026-08-16 20:06   ` Eduard Zingerman
2026-08-14 21:52 ` [PATCH bpf-next v2 5/6] selftests/bpf: Add tests for pointer type merge at a shared load Daniel Borkmann
2026-08-14 22:56   ` bot+bpf-ci
2026-08-14 23:35     ` Daniel Borkmann
2026-08-16 22:24   ` Eduard Zingerman [this message]
2026-08-16 22:32   ` Eduard Zingerman
2026-08-14 21:53 ` [PATCH bpf-next v2 6/6] selftests/bpf: Add tests for fault prone loads out of RCU pointers Daniel Borkmann
2026-08-14 22:03   ` sashiko-bot
2026-08-14 22:28     ` Daniel Borkmann
2026-08-16 22:24   ` Eduard Zingerman
2026-08-14 22:15 ` [PATCH bpf-next v2 1/6] bpf: Keep fault protection when merging pointer types sashiko-bot
2026-08-14 22:19   ` Daniel Borkmann
2026-08-16 19:42 ` Eduard Zingerman

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=99df26bd743e221a9b2d260546d30d73e5b80405.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=memxor@gmail.com \
    /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