Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Thu, 10 Oct 2024 14:17:30 -0700 you wrote:
> Libbpf pre-1.0 had a legacy logic of allowing singular non-annotated
> (i.e., not having explicit SEC() annotation) function to be treated as
> sole entry BPF program (unless there were other explicit entry
> programs).
>
> This behavior was dropped during libbpf 1.0 transition period (unless
> LIBBPF_STRICT_SEC_NAME flag was unset in libbpf_mode). When 1.0 was
> released and all the legacy behavior was removed, the bug slipped
> through leaving this legacy behavior around.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: never interpret subprogs in .text as entry programs
https://git.kernel.org/bpf/bpf-next/c/db089c9158c1
- [bpf-next,2/2] selftests/bpf: add subprog to BPF object file with no entry programs
https://git.kernel.org/bpf/bpf-next/c/82370ed5ade5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
