From: Leon Hwang <leon.hwang@linux.dev>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
yonghong.song@linux.dev, song@kernel.org, eddyz87@gmail.com,
me@manjusaka.me, leon.hwang@linux.dev, kernel-patches-bot@fb.com
Subject: [PATCH bpf-next v3 3/4] bpf, libbpf: Capture and log freplace attachment failure
Date: Mon, 17 Feb 2025 23:43:17 +0800 [thread overview]
Message-ID: <20250217154318.76145-4-leon.hwang@linux.dev> (raw)
In-Reply-To: <20250217154318.76145-1-leon.hwang@linux.dev>
To improve debugging, this patch captures logs when a freplace program
fails to attach. It provides a buffer to store the log and prints it using
pr_warn, making failure reasons more visible.
Changes:
* Extended bpf_attr and bpf_link_create_opts to include a log buffer for
tracing.
* Updated bpf_link_create() to handle log buffer properly.
* Modified bpf_program__attach_freplace() to store and print attachment
failure log.
Example output:
prog 'new_test_pkt_access': attach log: subprog_tail() is not a global function
This helps diagnose freplace attachment failures more efficiently.
Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
---
tools/include/uapi/linux/bpf.h | 2 ++
tools/lib/bpf/bpf.c | 6 +++++-
tools/lib/bpf/bpf.h | 2 ++
tools/lib/bpf/libbpf.c | 14 ++++++++++++--
4 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index fff6cdb8d11a2..bea4d802d4463 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -1759,6 +1759,8 @@ union bpf_attr {
* accessible through bpf_get_attach_cookie() BPF helper
*/
__u64 cookie;
+ __aligned_u64 log_buf; /* user supplied buffer */
+ __u32 log_size; /* size of user buffer */
} tracing;
struct {
__u32 pf;
diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c
index 359f73ead6137..cd422ecd53ae2 100644
--- a/tools/lib/bpf/bpf.c
+++ b/tools/lib/bpf/bpf.c
@@ -741,7 +741,7 @@ int bpf_link_create(int prog_fd, int target_fd,
if (iter_info_len || target_btf_id) {
if (iter_info_len && target_btf_id)
return libbpf_err(-EINVAL);
- if (!OPTS_ZEROED(opts, target_btf_id))
+ if (!OPTS_ZEROED(opts, tracing))
return libbpf_err(-EINVAL);
}
@@ -753,6 +753,8 @@ int bpf_link_create(int prog_fd, int target_fd,
if (target_btf_id) {
attr.link_create.target_btf_id = target_btf_id;
+ attr.link_create.tracing.log_buf = ptr_to_u64(OPTS_GET(opts, tracing.log_buf, 0));
+ attr.link_create.tracing.log_size = OPTS_GET(opts, tracing.log_size, 0);
goto proceed;
}
@@ -794,6 +796,8 @@ int bpf_link_create(int prog_fd, int target_fd,
case BPF_MODIFY_RETURN:
case BPF_LSM_MAC:
attr.link_create.tracing.cookie = OPTS_GET(opts, tracing.cookie, 0);
+ attr.link_create.tracing.log_buf = 0;
+ attr.link_create.tracing.log_size = 0;
if (!OPTS_ZEROED(opts, tracing))
return libbpf_err(-EINVAL);
break;
diff --git a/tools/lib/bpf/bpf.h b/tools/lib/bpf/bpf.h
index 435da95d20589..daf62f1bda80f 100644
--- a/tools/lib/bpf/bpf.h
+++ b/tools/lib/bpf/bpf.h
@@ -421,6 +421,8 @@ struct bpf_link_create_opts {
} uprobe_multi;
struct {
__u64 cookie;
+ const char *log_buf;
+ __u32 log_size;
} tracing;
struct {
__u32 pf;
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 194809da51725..f9266bd0ff709 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -12841,6 +12841,8 @@ struct bpf_link *bpf_program__attach_freplace(const struct bpf_program *prog,
int target_fd,
const char *attach_func_name)
{
+ struct bpf_link *link;
+ char log_buf[64];
int btf_id;
if (!!target_fd != !!attach_func_name) {
@@ -12862,10 +12864,18 @@ struct bpf_link *bpf_program__attach_freplace(const struct bpf_program *prog,
if (btf_id < 0)
return libbpf_err_ptr(btf_id);
+ log_buf[0] = '\0';
target_opts.target_btf_id = btf_id;
-
- return bpf_program_attach_fd(prog, target_fd, "freplace",
+ target_opts.tracing.log_buf = log_buf;
+ target_opts.tracing.log_size = sizeof(log_buf);
+ link = bpf_program_attach_fd(prog, target_fd, "freplace",
&target_opts);
+ if (libbpf_get_error(link) && log_buf[0] != '\0') {
+ log_buf[sizeof(log_buf)-1] = '\0';
+ log_buf[sizeof(log_buf)-2] = '\n';
+ pr_warn("prog '%s': attach log: %s", prog->name, log_buf);
+ }
+ return link;
} else {
/* no target, so use raw_tracepoint_open for compatibility
* with old kernels
--
2.47.1
next prev parent reply other threads:[~2025-02-17 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:43 [PATCH bpf-next v3 0/4] bpf: Improve error reporting for freplace attachment failure Leon Hwang
2025-02-17 15:43 ` [PATCH bpf-next v3 1/4] bpf, verifier: Add missing newline of bpf_log in bpf_check_attach_target Leon Hwang
2025-02-17 15:43 ` [PATCH bpf-next v3 2/4] bpf: Improve error reporting for freplace attachment failure Leon Hwang
2025-02-18 3:01 ` Alexei Starovoitov
2025-02-18 3:29 ` Leon Hwang
2025-02-17 15:43 ` Leon Hwang [this message]
2025-02-17 15:43 ` [PATCH bpf-next v3 4/4] selftests/bpf: Add test case for freplace attachment failure logging Leon Hwang
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=20250217154318.76145-4-leon.hwang@linux.dev \
--to=leon.hwang@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-patches-bot@fb.com \
--cc=me@manjusaka.me \
--cc=song@kernel.org \
--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