From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com, Ilya Leoshkevich <iii@linux.ibm.com>,
Kenta Tada <kenta.tada@sony.com>,
Hengqi Chen <hengqi.chen@gmail.com>
Subject: Re: [PATCH RFC bpf-next 2/3] libbpf: add ksyscall/kretsyscall sections support for syscall kprobes
Date: Fri, 8 Jul 2022 11:35:09 +0200 [thread overview]
Message-ID: <Ysf6TRzh9hgsAjep@krava> (raw)
In-Reply-To: <20220707004118.298323-3-andrii@kernel.org>
On Wed, Jul 06, 2022 at 05:41:17PM -0700, Andrii Nakryiko wrote:
SNIP
> +static int probe_kern_syscall_wrapper(void)
> +{
> + /* available_filter_functions is a few times smaller than
> + * /proc/kallsyms and has simpler format, so we use it as a faster way
> + * to check that __<arch>_sys_bpf symbol exists, which is a sign that
> + * kernel was built with CONFIG_ARCH_HAS_SYSCALL_WRAPPER and uses
> + * syscall wrappers
> + */
> + static const char *kprobes_file = "/sys/kernel/tracing/available_filter_functions";
> + char func_name[128], syscall_name[128];
> + const char *ksys_pfx;
> + FILE *f;
> + int cnt;
> +
> + ksys_pfx = arch_specific_syscall_pfx();
> + if (!ksys_pfx)
> + return 0;
> +
> + f = fopen(kprobes_file, "r");
> + if (!f)
> + return 0;
> +
> + snprintf(syscall_name, sizeof(syscall_name), "__%s_sys_bpf", ksys_pfx);
> +
> + /* check if bpf() syscall wrapper is listed as possible kprobe */
> + while ((cnt = fscanf(f, "%127s%*[^\n]\n", func_name)) == 1) {
nit cnt is not used/needed
jirka
> + if (strcmp(func_name, syscall_name) == 0) {
> + fclose(f);
> + return 1;
> + }
> + }
> +
> + fclose(f);
> + return 0;
> +}
> +
> enum kern_feature_result {
> FEAT_UNKNOWN = 0,
> FEAT_SUPPORTED = 1,
> @@ -4722,6 +4781,9 @@ static struct kern_feature_desc {
> [FEAT_BTF_ENUM64] = {
> "BTF_KIND_ENUM64 support", probe_kern_btf_enum64,
> },
> + [FEAT_SYSCALL_WRAPPER] = {
> + "Kernel using syscall wrapper", probe_kern_syscall_wrapper,
> + },
> };
>
SNIP
next prev parent reply other threads:[~2022-07-08 9:35 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 [this message]
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
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=Ysf6TRzh9hgsAjep@krava \
--to=olsajiri@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