Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@xxxxxxxxxx>:
On Thu, 8 Feb 2024 18:37:46 -0800 you wrote:
> From: Kui-Feng Lee <thinker.li@xxxxxxxxx>
>
> Allow passing null pointers to the operators provided by a struct_ops
> object. This is an RFC to collect feedbacks/opinions.
>
> The function pointers that are passed to struct_ops operators (the function
> pointers) are always considered reliable until now. They cannot be
> null. However, in certain scenarios, it should be possible to pass null
> pointers to these operators. For instance, sched_ext may pass a null
> pointer in the struct task type to an operator that is provided by its
> struct_ops objects.
>
> [...]
Here is the summary with links:
- [bpf-next,v8,1/4] bpf: add btf pointer to struct bpf_ctx_arg_aux.
https://git.kernel.org/bpf/bpf-next/c/77c0208e199c
- [bpf-next,v8,2/4] bpf: Move __kfunc_param_match_suffix() to btf.c.
https://git.kernel.org/bpf/bpf-next/c/6115a0aeef01
- [bpf-next,v8,3/4] bpf: Create argument information for nullable arguments.
https://git.kernel.org/bpf/bpf-next/c/1611603537a4
- [bpf-next,v8,4/4] selftests/bpf: Test PTR_MAYBE_NULL arguments of struct_ops operators.
https://git.kernel.org/bpf/bpf-next/c/00f239eccf46
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
