From: Jiri Olsa <olsajiri@gmail.com>
To: KaFai Wan <mannkafai@gmail.com>
Cc: martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
mykolal@fb.com, shuah@kernel.org, memxor@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kafai.wan@hotmail.com,
leon.hwang@linux.dev
Subject: Re: [PATCH bpf-next 1/2] bpf: Allow access to const void pointer arguments in tracing programs
Date: Mon, 14 Apr 2025 12:35:05 +0200 [thread overview]
Message-ID: <Z_zk2ZaG5fRRFQio@krava> (raw)
In-Reply-To: <20250412170626.3638516-2-kafai.wan@hotmail.com>
On Sun, Apr 13, 2025 at 01:06:25AM +0800, KaFai Wan wrote:
> Adding support to access arguments with const void pointer arguments
> in tracing programs.
>
> Currently we allow tracing programs to access void pointers. If we try to
> access argument which is pointer to const void like 2nd argument in kfree,
> verifier will fail to load the program with;
>
> 0: R1=ctx() R10=fp0
> ; asm volatile ("r2 = *(u64 *)(r1 + 8); ");
> 0: (79) r2 = *(u64 *)(r1 +8)
> func 'kfree' arg1 type UNKNOWN is not a struct
>
> Adding is_void_ptr to generic void pointer check.
>
> Cc: Leon Hwang <leon.hwang@linux.dev>
> Signed-off-by: KaFai Wan <kafai.wan@hotmail.com>
> ---
> kernel/bpf/btf.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index 16ba36f34dfa..e11d3afd0562 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -6383,6 +6383,14 @@ struct btf *bpf_prog_get_target_btf(const struct bpf_prog *prog)
> return prog->aux->attach_btf;
> }
>
> +static bool is_void_ptr(struct btf *btf, const struct btf_type *t)
> +{
> + /* skip modifiers */
> + t = btf_type_skip_modifiers(btf, t->type, NULL);
> +
> + return t->type == 0;
I think you can use btf_type_is_void in here
> +}
> +
> static bool is_int_ptr(struct btf *btf, const struct btf_type *t)
> {
> /* skip modifiers */
> @@ -6776,7 +6784,7 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
> }
> }
>
> - if (t->type == 0)
> + if (is_void_ptr(btf, t))
lgtm,
nit, the is_void_ptr name suggest there's also ptr check in the helper function,
which is not the case. I understand it follows is_int_ptr name, but perhaps we
could rename both helpers to is_void and is_int ... feel free to ignore ;-)
jirka
> /* This is a pointer to void.
> * It is the same as scalar from the verifier safety pov.
> * No further pointer walking is allowed.
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-14 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 17:06 [PATCH bpf-next 0/2] bpf: Allow access to const void pointer arguments in tracing programs KaFai Wan
2025-04-12 17:06 ` [PATCH bpf-next 1/2] " KaFai Wan
2025-04-14 10:35 ` Jiri Olsa [this message]
2025-04-15 14:37 ` Kafai Wan
2025-04-12 17:06 ` [PATCH bpf-next 2/2] selftests/bpf: Add test to access const void pointer argument in tracing program KaFai Wan
2025-04-14 10:35 ` Jiri Olsa
2025-04-15 14:31 ` Kafai Wan
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=Z_zk2ZaG5fRRFQio@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai.wan@hotmail.com \
--cc=kpsingh@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mannkafai@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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