Re: [PATCH bpf-next v5 0/3] bpf: Warn with __bpf_trap() kfunc maybe due to uninitialized variable

patchwork-bot+netdevbpf
2025-05-27T17:40:00Z

Hello:

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

On Fri, 23 May 2025 13:53:16 -0700 you wrote:
> Marc Suñé (Isovalent, part of Cisco) reported an issue where an
> uninitialized variable caused generating bpf prog binary code not
> working as expected. The reproducer is in [1] where the flags
> “-Wall -Werror” are enabled, but there is no warning as the compiler
> takes advantage of uninitialized variable to do aggressive optimization.
> Such optimization results in a verification log:
> last insn is not an exit or jmp
> User still needs to take quite some time to figure out what is
> the root cause.
>
> [...]

Here is the summary with links:
- [bpf-next,v5,1/3] bpf: Remove special_kfunc_set from verifier
https://git.kernel.org/bpf/bpf-next/c/d848bba68034
- [bpf-next,v5,2/3] bpf: Warn with __bpf_trap() kfunc maybe due to uninitialized variable
https://git.kernel.org/bpf/bpf-next/c/f95695f2c465
- [bpf-next,v5,3/3] selftests/bpf: Add unit tests with __bpf_trap() kfunc
https://git.kernel.org/bpf/bpf-next/c/92de53d247df

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.