All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yan Zhai <yan@cloudflare.com>
To: bpf@vger.kernel.org
Cc: kernel-team@cloudflare.com
Subject: Ideal way to read FUNC_PROTO in raw tp?
Date: Thu, 6 Jun 2024 15:03:29 -0700	[thread overview]
Message-ID: <ZmIyMfRSp9DpU7dF@debian.debian> (raw)

Hi,

 I am building a tracing program around workqueue. But I encountered
following problem when I try to record a function pointer value from
trace_workqueue_execute_end on net-next kernel:

...
libbpf: prog 'workqueue_end': BPF program load failed: Permission
denied
libbpf: prog 'workqueue_end': -- BEGIN PROG LOAD LOG --
reg type unsupported for arg#0 function workqueue_end#5
0: R1=ctx(off=0,imm=0) R10=fp0
; int BPF_PROG(workqueue_end, struct work_struct *w, work_func_t f)
0: (79) r3 = *(u64 *)(r1 +8)
func 'workqueue_execute_end' arg1 type FUNC_PROTO is not a struct
invalid bpf_context access off=8 size=8
processed 1 insns (limit 1000000) max_states_per_insn 0 total_states 0
peak_states 0 mark_read 0
-- END PROG LOAD LOG --
libbpf: prog 'workqueue_end': failed to load: -13
libbpf: failed to load object 'configs/test.bpf.o'
Error: failed to load object file
Warning: bpftool is now running in libbpf strict mode and has more
stringent requirements about BPF programs.
If it used to work for this object file but now doesn't, see --legacy
option for more details.
...

A simple reproducer for me is like:
#include "vmlinux.h"
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_tracing.h>

SEC("tp_btf/workqueue_execute_end")
int BPF_PROG(workqueue_end, struct work_struct *w, work_func_t f)
{
        u64 addr = (u64) f;
        bpf_printk("f is %lu\n", addr);

        return 0;
}

char LICENSE[] SEC("license") = "GPL";

I would like to use the function address to decode the kernel symbol
and track execution of these functions. Replacing raw tp to regular tp
solves the problem, but I am wondering if there is any go-to approach
to read the pointer value in a raw tp? Doesn't seem to find one in
selftests/samples. If not, does it make sense if we allow it in
the verifier for tracing programs like the attached patch?

Yan

---
diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
index 821063660d9f..5f000ab4c8d0 100644
--- a/kernel/bpf/btf.c
+++ b/kernel/bpf/btf.c
@@ -6308,6 +6308,11 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
                        __btf_name_by_offset(btf, t->name_off),
                        btf_type_str(t));
                return false;
+       } else if (prog->type == BPF_PROG_TYPE_TRACING || prog->type == BPF_PROG_TYPE_RAW_TRACEPOINT) {
+               /* allow reading function pointer value from a tracing program */
+               const struct btf_type *pointed = btf_type_by_id(btf, t->type);
+               if (btf_type_is_func_proto(pointed))
+                       return true;
        }

        /* check for PTR_TO_RDONLY_BUF_OR_NULL or PTR_TO_RDWR_BUF_OR_NULL */

             reply	other threads:[~2024-06-06 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 22:03 Yan Zhai [this message]
2024-06-15  1:04 ` Ideal way to read FUNC_PROTO in raw tp? Alexei Starovoitov
2024-06-20  1:57   ` Yan Zhai
2024-06-21 22:04 ` Andrii Nakryiko
2024-06-25  3:00   ` Yan Zhai

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=ZmIyMfRSp9DpU7dF@debian.debian \
    --to=yan@cloudflare.com \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@cloudflare.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.