Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <[email protected]>:
On Mon, 2 Mar 2026 15:08:34 -0500 you wrote:
> When libbpf attaches kprobe.session programs with exact function names
> (the common case: SEC("kprobe.session/vfs_read")), the current code path
> has two independent performance bottlenecks:
>
> 1. Userspace (libbpf): attach_kprobe_session() always parses
> /proc/kallsyms to resolve function names, even when the name is exact
> (no wildcards). This takes ~150ms per function.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] libbpf: Optimize kprobe.session attachment for exact
function names
https://git.kernel.org/bpf/bpf-next/c/6afc431db1b4
- [bpf-next,v4,2/3] ftrace: Use kallsyms binary search for single-symbol
lookup
(no matching commit)
- [bpf-next,v4,3/3] selftests/bpf: add tests for kprobe.session optimization
https://git.kernel.org/bpf/bpf-next/c/a28441dd2961
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
