Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <[email protected]>:
On Tue, 7 Apr 2026 16:39:10 -0400 you wrote:
> When a kernel module exports a symbol with the same name as an existing
> vmlinux symbol, kprobe attachment fails with -EADDRNOTAVAIL because
> number_of_same_symbols() counts matches across both vmlinux and all
> loaded modules, returning a count greater than 1.
>
> This series takes a different approach from v1-v4, which implemented a
> libbpf-side fallback parsing /proc/kallsyms and retrying with the
> absolute address. That approach was rejected (Andrii Nakryiko, Ihor
> Solodrai) because ambiguous symbol resolution does not belong in libbpf.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/2] tracing: Prefer vmlinux symbols over module symbols for
unqualified kprobes
https://git.kernel.org/bpf/bpf-next/c/1870ddcd94b0
- [bpf-next,v7,2/2] selftests/bpf: Add tests for kprobe attachment with
duplicate symbols
https://git.kernel.org/bpf/bpf-next/c/cea4323f1cfe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
