Re: [PATCH bpf-next v3 0/3] Handle possible NULL trusted raw_tp arguments

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon,  4 Nov 2024 09:19:56 -0800 you wrote:
> More context is available in [0], but the TLDR; is that the verifier
> incorrectly assumes that any raw tracepoint argument will always be
> non-NULL. This means that even when users correctly check possible NULL
> arguments, the verifier can remove the NULL check due to incorrect
> knowledge of the NULL-ness of the pointer. Secondly, kernel helpers or
> kfuncs taking these trusted tracepoint arguments incorrectly assume that
> all arguments will always be valid non-NULL.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/3] bpf: Mark raw_tp arguments with PTR_MAYBE_NULL
    https://git.kernel.org/bpf/bpf-next/c/cb4158ce8ec8
  - [bpf-next,v3,2/3] selftests/bpf: Clean up open-coded gettid syscall invocations
    https://git.kernel.org/bpf/bpf-next/c/0e2fb011a0ba
  - [bpf-next,v3,3/3] selftests/bpf: Add tests for raw_tp null handling
    https://git.kernel.org/bpf/bpf-next/c/d798ce3f4cab

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