Re: [PATCH bpf-next v2 1/2] bpf: check_cond_jmp_op(): properly infer if register is null

[patchwork-bot+netdevbpf@kernel.org]

Hello:

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

On Wed, 26 Aug 2026 11:18:44 -0700 you wrote:
> Nicholas Carlini reported a bug when verifier can incorrectly infer
> that a pointer is non-null. The bug occurs when two pointers are
> compared and one of them has a type w/o PTR_MAYBE_NULL flag,
> but which allows a value to be NULL at runtime.
> Here is an example:
> 
>   // `a` is PTR_TO_MEM | MEM_RDONLY | PTR_UNTRUSTED
>   // `a` is 0 at runtime.
>   // `b` is PTR_TO_MAP_VALUE | PTR_MAYBE_NULL
>   void *a = bpf_rdonly_cast(0, 0);
>   int  *b = bpf_map_lookup_elem(...);
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: check_cond_jmp_op(): properly infer if register is null
    https://git.kernel.org/bpf/bpf/c/d3ef6c097ba0
  - [bpf-next,v2,2/2] selftests/bpf: a demo for check_cond_jmp_op() non-null inference bug
    https://git.kernel.org/bpf/bpf/c/ce6dcd0aed18

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