Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Tue, 18 Oct 2022 17:28:13 -0700 you wrote:
> Make libbpf more conservative in using BPF_F_MMAPABLE flag with internal BPF
> array maps that are backing global data sections. See patch #2 for full
> description and justification.
>
> Changes in this dataset support having bpf_spinlock, kptr, rb_tree nodes and
> other "special" variables as global variables. Combining this with libbpf's
> existing support for multiple custom .data.* sections allows BPF programs to
> utilize multiple spinlock/rbtree_node/kptr variables in a pretty natural way
> by just putting all such variables into separate data sections (and thus ARRAY
> maps).
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/3] libbpf: clean up and refactor BTF fixup step
https://git.kernel.org/bpf/bpf-next/c/f33f742d5674
- [v2,bpf-next,2/3] libbpf: only add BPF_F_MMAPABLE flag for data maps with global vars
https://git.kernel.org/bpf/bpf-next/c/4fcac46c7e10
- [v2,bpf-next,3/3] libbpf: add non-mmapable data section selftest
https://git.kernel.org/bpf/bpf-next/c/2f968e9f4a95
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
