From: Alan Maguire <alan.maguire@oracle.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
Kenta Tada <kenta.tada@sony.com>,
Hengqi Chen <hengqi.chen@gmail.com>
Subject: Re: [PATCH RFC bpf-next 0/3] libbpf: add better syscall kprobing support
Date: Wed, 13 Jul 2022 08:12:36 +0100 [thread overview]
Message-ID: <eb339ec7-9d7c-b96e-179e-b84751499808@oracle.com> (raw)
In-Reply-To: <CAEf4Bzb=oT5PzYjM+aDeAg76yB8KpROWcdanqLZ+G6qtdFsAqA@mail.gmail.com>
On 12/07/2022 05:24, Andrii Nakryiko wrote:
> Sounds good! I'll add that to bpf_program__attach_ksyscall() doc
> comment (and to commit message). I'll implement those new virtual
> __kconfig variables that I mentioned in another thread and post it as
> v1, hopefully some time this week.
>
This is really useful, thanks for doing it! I tested on arm64,
only issue was the tracefs path issue that I think was already
mentioned, i.e. for me it took
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 4749fb84e33d..a27f21619cfc 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -4685,7 +4685,7 @@ static int probe_kern_syscall_wrapper(void)
* kernel was built with CONFIG_ARCH_HAS_SYSCALL_WRAPPER and uses
* syscall wrappers
*/
- static const char *kprobes_file = "/sys/kernel/tracing/available_filter_functions";
+ static const char *kprobes_file = "/sys/kernel/debug/tracing/available_filter_functions";
char func_name[128], syscall_name[128];
const char *ksys_pfx;
FILE *f;
...to get the feature probing - and hence auto-attach to the
right arch-specific probes - to work.
Alan
next prev parent reply other threads:[~2022-07-13 7:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 0:41 [PATCH RFC bpf-next 0/3] libbpf: add better syscall kprobing support Andrii Nakryiko
2022-07-07 0:41 ` [PATCH RFC bpf-next 1/3] libbpf: improve and rename BPF_KPROBE_SYSCALL Andrii Nakryiko
2022-07-07 0:41 ` [PATCH RFC bpf-next 2/3] libbpf: add ksyscall/kretsyscall sections support for syscall kprobes Andrii Nakryiko
2022-07-07 17:23 ` Alexei Starovoitov
2022-07-07 19:10 ` Andrii Nakryiko
2022-07-07 19:36 ` Alexei Starovoitov
2022-07-07 20:50 ` Andrii Nakryiko
2022-07-08 11:28 ` Jiri Olsa
2022-07-08 22:05 ` Andrii Nakryiko
2022-07-10 0:38 ` Alexei Starovoitov
2022-07-11 16:28 ` Andrii Nakryiko
2022-07-12 4:20 ` Alexei Starovoitov
2022-07-12 5:00 ` Andrii Nakryiko
2022-07-08 9:35 ` Jiri Olsa
2022-07-08 22:04 ` Andrii Nakryiko
2022-07-07 0:41 ` [PATCH RFC bpf-next 3/3] selftests/bpf: use BPF_KSYSCALL and SEC("ksyscall") in selftests Andrii Nakryiko
2022-07-07 8:28 ` [PATCH RFC bpf-next 0/3] libbpf: add better syscall kprobing support Yaniv Agman
2022-07-07 20:56 ` Andrii Nakryiko
2022-07-11 16:23 ` Andrii Nakryiko
2022-07-07 15:51 ` Ilya Leoshkevich
2022-07-07 20:59 ` Andrii Nakryiko
2022-07-11 18:25 ` Ilya Leoshkevich
2022-07-12 4:24 ` Andrii Nakryiko
2022-07-13 7:12 ` Alan Maguire [this message]
2022-07-13 17:52 ` Andrii Nakryiko
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=eb339ec7-9d7c-b96e-179e-b84751499808@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hengqi.chen@gmail.com \
--cc=iii@linux.ibm.com \
--cc=kenta.tada@sony.com \
--cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox