All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: eddyz87@gmail.com, memxor@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 1/3] selftests/bpf: Add tests for pointer type merge at a shared load
Date: Mon, 17 Aug 2026 19:00:29 +0000	[thread overview]
Message-ID: <178699322930.1691257.556829959500031509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817141015.878071-1-daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Mon, 17 Aug 2026 16:10:13 +0200 you 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
>   [...]
>   #242/1   mem_rdonly_untrusted/btf_id_to_ptr_mem:OK
>   #242/2   mem_rdonly_untrusted/ldx_is_ok_bad_addr:OK
>   #242/3   mem_rdonly_untrusted/ldx_is_ok_good_addr:OK
>   #242/4   mem_rdonly_untrusted/offset_not_tracked:OK
>   #242/5   mem_rdonly_untrusted/stx_not_ok:OK
>   #242/6   mem_rdonly_untrusted/atomic_not_ok:OK
>   #242/7   mem_rdonly_untrusted/atomic_rmw_not_ok:OK
>   #242/8   mem_rdonly_untrusted/kfunc_param_not_ok:OK
>   #242/9   mem_rdonly_untrusted/mixed_mem_type:OK
>   #242/10  mem_rdonly_untrusted/mixed_mem_untrusted_btf_id_type:OK
>   #242/11  mem_rdonly_untrusted/mixed_mem_btf_id_type:OK
>   #242/12  mem_rdonly_untrusted/mixed_rdonly_mem_btf_id_type:OK
>   #242/13  mem_rdonly_untrusted/mixed_mem_mem_type:OK
>   #242/14  mem_rdonly_untrusted/mixed_map_value_mem_type:OK
>   #242/15  mem_rdonly_untrusted/mixed_stack_mem_type:OK
>   #242/16  mem_rdonly_untrusted/diff_size_access:OK
>   #242/17  mem_rdonly_untrusted/misaligned_access:OK
>   #242/18  mem_rdonly_untrusted/null_check:OK
>   #242/19  mem_rdonly_untrusted/ldx_is_ok_commuted_addr:OK
>   #242/20  mem_rdonly_untrusted/helper_param_not_ok:OK
>   #242     mem_rdonly_untrusted:OK
>   Summary: 1/20 PASSED, 0 SKIPPED, 0/0 FAILED
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/3] selftests/bpf: Add tests for pointer type merge at a shared load
    https://git.kernel.org/bpf/bpf-next/c/78d8e5b375c0
  - [bpf-next,v3,2/3] selftests/bpf: Add tests for fault prone loads out of RCU pointers
    https://git.kernel.org/bpf/bpf-next/c/2b918fe2f11f
  - [bpf-next,v3,3/3] selftests/bpf: Add tests for a store on a fault prone qdisc pointer
    https://git.kernel.org/bpf/bpf-next/c/f79066c78402

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



      parent reply	other threads:[~2026-08-17 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 14:10 [PATCH bpf-next v3 1/3] selftests/bpf: Add tests for pointer type merge at a shared load Daniel Borkmann
2026-08-17 14:10 ` [PATCH bpf-next v3 2/3] selftests/bpf: Add tests for fault prone loads out of RCU pointers Daniel Borkmann
2026-08-17 14:10 ` [PATCH bpf-next v3 3/3] selftests/bpf: Add tests for a store on a fault prone qdisc pointer Daniel Borkmann
2026-08-17 19:00 ` patchwork-bot+netdevbpf [this message]

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=178699322930.1691257.556829959500031509.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.