Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Thu, 13 Jun 2024 14:18:12 -0700 you wrote:
> Current verifier checks for the arg to be nullable after checking for
> certain pointer types. It prevents programs to pass NULL to kfunc args
> even if they are marked as nullable. This patchset adjusts verifier and
> changes bpf crypto kfuncs to allow null for IV parameter which is
> optional for some ciphers. Benchmark shows ~4% improvements when there
> is no need to initialise 0-sized dynptr.
>
> [...]
Here is the summary with links:
- [RESEND,bpf-next,v3,1/5] bpf: verifier: make kfuncs args nullalble
https://git.kernel.org/bpf/bpf-next/c/a90797993afc
- [RESEND,bpf-next,v3,2/5] bpf: crypto: make state and IV dynptr nullable
https://git.kernel.org/bpf/bpf-next/c/65d6d61d2596
- [RESEND,bpf-next,v3,3/5] selftests: bpf: crypto: use NULL instead of 0-sized dynptr
https://git.kernel.org/bpf/bpf-next/c/9363dc8ddc4e
- [RESEND,bpf-next,v3,4/5] selftests: bpf: crypto: adjust bench to use nullable IV
https://git.kernel.org/bpf/bpf-next/c/9b560751f75f
- [RESEND,bpf-next,v3,5/5] selftests: bpf: add testmod kfunc for nullable params
https://git.kernel.org/bpf/bpf-next/c/2d45ab1eda46
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
