Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:
On Thu, 9 Jan 2025 09:40:23 -0800 you wrote:
> Jordan reported an issue in Meta production environment where func
> try_to_wake_up() is renamed to try_to_wake_up.llvm.<hash>() by clang
> compiler at lto mode. The original 'kprobe/try_to_wake_up' does not
> work any more since try_to_wake_up() does not match the actual func
> name in /proc/kallsyms.
>
> There are a couple of ways to resolve this issue. For example, in
> attach_kprobe(), we could do lookup in /proc/kallsyms so try_to_wake_up()
> can be replaced by try_to_wake_up.llvm.<hach>(). Or we can force users
> to use bpf_program__attach_kprobe() where they need to lookup
> /proc/kallsyms to find out try_to_wake_up.llvm.<hach>(). But these two
> approaches requires extra work by either libbpf or user.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] libbpf: Add unique_match option for multi kprobe
https://git.kernel.org/bpf/bpf-next/c/e2b0bda62d54
- [bpf-next,v2,2/2] selftests/bpf: Add a test for kprobe multi with unique_match
https://git.kernel.org/bpf/bpf-next/c/a43796b52012
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
