Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@xxxxxxxxxxxxx>:
On Thu, 17 Aug 2023 15:53:52 -0700 you wrote:
> The function signature of kfuncs can change at any time due to their
> intentional lack of stability guarantees. As kfuncs become more widely
> used, BPF program writers will need facilities to support calling
> different versions of a kfunc from a single BPF object. Consider this
> simplified example based on a real scenario we ran into at Meta:
>
> /* initial kfunc signature */
> int some_kfunc(void *ptr)
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/2] libbpf: Support triple-underscore flavors for kfunc relocation
https://git.kernel.org/bpf/bpf-next/c/5964a223f5e4
- [v3,bpf-next,2/2] selftests/bpf: Add CO-RE relocs kfunc flavors tests
https://git.kernel.org/bpf/bpf-next/c/63ae8eb2c5b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
