From: patchwork-bot+netdevbpf@kernel.org
To: Hoyeon Lee <hoyeon.lee@suse.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, shuah@kernel.org, yangfeng@kylinos.cn,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v7 0/3] libbpf: clarify raw-address single kprobe attach behavior
Date: Thu, 02 Apr 2026 20:30:09 +0000 [thread overview]
Message-ID: <177516180954.605612.3114427119348580758.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401143116.185049-1-hoyeon.lee@suse.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
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
prev parent reply other threads:[~2026-04-02 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:29 [PATCH bpf-next v7 0/3] libbpf: clarify raw-address single kprobe attach behavior Hoyeon Lee
2026-04-01 14:29 ` [PATCH bpf-next v7 1/3] libbpf: use direct error codes for kprobe/uprobe attach Hoyeon Lee
2026-04-01 14:29 ` [PATCH bpf-next v7 2/3] libbpf: clarify raw-address single kprobe attach behavior Hoyeon Lee
2026-04-01 14:29 ` [PATCH bpf-next v7 3/3] selftests/bpf: add test for raw-address single kprobe attach Hoyeon Lee
2026-04-02 20:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177516180954.605612.3114427119348580758.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hoyeon.lee@suse.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yangfeng@kylinos.cn \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox