Hello:
This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov ast@kernel.org:
On Tue, 14 Jan 2025 13:28:41 -0700 you wrote:
This patch allows progs to elide a null check on statically known map lookup keys. In other words, if the verifier can statically prove that the lookup will be in-bounds, allow the prog to drop the null check.
This is useful for two reasons:
- Large numbers of nullness checks (especially when they cannot fail) unnecessarily pushes prog towards BPF_COMPLEXITY_LIMIT_JMP_SEQ.
- It forms a tighter contract between programmer and verifier.
[...]
Here is the summary with links: - [bpf-next,v7,1/5] bpf: verifier: Add missing newline on verbose() call https://git.kernel.org/bpf/bpf-next/c/b8a81b5dd645 - [bpf-next,v7,2/5] bpf: tcp: Mark bpf_load_hdr_opt() arg2 as read-write https://git.kernel.org/bpf/bpf-next/c/8ac412a33611 - [bpf-next,v7,3/5] bpf: verifier: Refactor helper access type tracking https://git.kernel.org/bpf/bpf-next/c/37cce22dbd51 - [bpf-next,v7,4/5] bpf: verifier: Support eliding map lookup nullness https://git.kernel.org/bpf/bpf-next/c/d2102f2f5d75 - [bpf-next,v7,5/5] bpf: selftests: verifier: Add nullness elision tests https://git.kernel.org/bpf/bpf-next/c/f932a8e4824b
You are awesome, thank you!