Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@xxxxxxxxxxxxx>:
On Tue, 23 Nov 2021 12:01:04 -0800 you wrote:
> Load global data maps lazily, if kernel is too old to support global
> data. Make sure that programs are still correct by detecting if any of
> the to-be-loaded programs have relocation against any of such maps.
>
> This allows to solve the issue ([0]) with bpf_printk() and Clang
> generating unnecessary and unreferenced .rodata.strX.Y sections, but it
> also goes further along the CO-RE lines, allowing to have a BPF object
> in which some code can work on very old kernels and relies only on BPF
> maps explicitly, while other BPF programs might enjoy global variable
> support. If such programs are correctly set to not load at runtime on
> old kernels, bpf_object will load and function correctly now.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/2] libbpf: load global data maps lazily on legacy kernels
https://git.kernel.org/bpf/bpf-next/c/16e0c35c6f7a
- [v2,bpf-next,2/2] selftests/bpf: mix legacy (maps) and modern (vars) BPF in one test
https://git.kernel.org/bpf/bpf-next/c/e4f7ac90c2b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
