Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Sun, 20 Nov 2022 11:54:21 -0800 you wrote:
> Currenty, a non-tracing bpf program typically has a single 'context' argument
> with predefined uapi struct type. Following these uapi struct, user is able
> to access other fields defined in uapi header. Inside the kernel, the
> user-seen 'context' argument is replaced with 'kernel context' (or 'kctx'
> in short) which can access more information than what uapi header provides.
> To access other info not in uapi header, people typically do two things:
> (1). extend uapi to access more fields rooted from 'context'.
> (2). use bpf_probe_read_kernl() helper to read particular field based on
> kctx.
> Using (1) needs uapi change and using (2) makes code more complex since
> direct memory access is not allowed.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/4] bpf: Add support for kfunc set with common btf_ids
https://git.kernel.org/bpf/bpf-next/c/cfe1456440c8
- [bpf-next,v4,2/4] bpf: Add a kfunc to type cast from bpf uapi ctx to kernel ctx
https://git.kernel.org/bpf/bpf-next/c/fd264ca02094
- [bpf-next,v4,3/4] bpf: Add a kfunc for generic type cast
https://git.kernel.org/bpf/bpf-next/c/a35b9af4ec2c
- [bpf-next,v4,4/4] bpf: Add type cast unit tests
https://git.kernel.org/bpf/bpf-next/c/58d84bee5846
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
