Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Mon, 8 Jul 2024 13:45:37 -0700 you wrote:
> Fix recently identified (but long standing) bug with handling BPF skeleton
> forward and backward compatibility. On libbpf side, even though BPF skeleton
> was always designed to be forward and backwards compatible through recording
> actual size of constrituents of BPF skeleton itself (map/prog/var skeleton
> definitions), libbpf implementation did implicitly hard-code those sizes by
> virtue of using a trivial array access syntax.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/3] bpftool: improve skeleton backwards compat with old buggy libbpfs
https://git.kernel.org/bpf/bpf-next/c/06e71ad53488
- [v2,bpf-next,2/3] libbpf: fix BPF skeleton forward/backward compat handling
https://git.kernel.org/bpf/bpf-next/c/99fb9531886d
- [v2,bpf-next,3/3] libbpf: improve old BPF skeleton handling for map auto-attach
https://git.kernel.org/bpf/bpf-next/c/a459f4bb27f2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
