[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173707983824.1659522.18019002875638405637.git-patchwork-notify@kernel.org>
Date: Fri, 17 Jan 2025 02:10:38 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel Xu <dxu@...uu.xyz>
Cc: linux-kernel@...r.kernel.org, bpf@...r.kernel.org, ast@...nel.org,
memxor@...il.com, daniel@...earbox.net, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, eddyz87@...il.com, andrii@...nel.org
Subject: Re: [PATCH bpf-next v7 0/5] Support eliding map lookup nullness
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.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:
>
> 1. Large numbers of nullness checks (especially when they cannot fail)
> unnecessarily pushes prog towards BPF_COMPLEXITY_LIMIT_JMP_SEQ.
> 2. 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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists