Re: [PATCH bpf-next v7 0/3] libbpf: clarify raw-address single kprobe attach behavior

[patchwork-bot+netdevbpf]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:

On Wed,  1 Apr 2026 23:29:28 +0900 you wrote:
> Today libbpf documents single-kprobe attach through func_name, with an
> optional offset. For the PMU-based path, func_name = NULL with an
> absolute address in offset already works as well, but that is not
> described in the API.
> 
> This patchset clarifies this behavior. First commit fixes kprobe
> and uprobe attach error handling to use direct error codes. Next adds
> kprobe API comments for the raw-address form and rejects it explicitly
> for legacy tracefs/debugfs kprobes. Last adds PERF and LINK selftests
> for the raw-address form, and checks that LEGACY rejects it.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,1/3] libbpf: use direct error codes for kprobe/uprobe attach
    https://git.kernel.org/bpf/bpf-next/c/f547cf79475f
  - [bpf-next,v7,2/3] libbpf: clarify raw-address single kprobe attach behavior
    https://git.kernel.org/bpf/bpf-next/c/e1621c752865
  - [bpf-next,v7,3/3] selftests/bpf: add test for raw-address single kprobe attach
    https://git.kernel.org/bpf/bpf-next/c/9d77cefe8fcd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html