Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 7 Oct 2020 17:10:20 -0700 you wrote:
> Patch set implements logic in libbpf to auto-adjust memory size (1-, 2-, 4-,
> 8-bytes) of load/store (LD/ST/STX) instructions which have BPF CO-RE field
> offset relocation associated with it. In practice this means transparent
> handling of 32-bit kernels, both pointer and unsigned integers. Signed
> integers are not relocatable with zero-extending loads/stores, so libbpf
> poisons them and generates a warning. If/when BPF gets support for
> sign-extending loads/stores, it would be possible to automatically relocate
> them as well.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/4] libbpf: skip CO-RE relocations for not loaded BPF programs
https://git.kernel.org/bpf/bpf-next/c/47f7cf6325f7
- [v3,bpf-next,2/4] libbpf: support safe subset of load/store instruction resizing with CO-RE
https://git.kernel.org/bpf/bpf-next/c/a66345bcbdf0
- [v3,bpf-next,3/4] libbpf: allow specifying both ELF and raw BTF for CO-RE BTF override
https://git.kernel.org/bpf/bpf-next/c/2b7d88c2b582
- [v3,bpf-next,4/4] selftests/bpf: validate libbpf's auto-sizing of LD/ST/STX instructions
https://git.kernel.org/bpf/bpf-next/c/888d83b961f6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
