bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Hwang" <leon.hwang@linux.dev>
To: "Amery Hung" <ameryhung@gmail.com>
Cc: <bpf@vger.kernel.org>, <ast@kernel.org>, <andrii@kernel.org>,
	<daniel@iogearbox.net>, <martin.lau@linux.dev>,
	<eddyz87@gmail.com>, <song@kernel.org>, <yonghong.song@linux.dev>,
	<yatsenko@meta.com>, <puranjay@kernel.org>,
	<davidzalman.101@gmail.com>, <cheick.traore@foss.st.com>,
	<chen.dylane@linux.dev>, <mika.westerberg@linux.intel.com>,
	<menglong8.dong@gmail.com>, <kernel-patches-bot@fb.com>
Subject: Re: [PATCH bpf-next v2 1/3] bpf: Allow union argument in trampoline based programs
Date: Wed, 17 Sep 2025 20:40:30 +0800	[thread overview]
Message-ID: <DCV2ZG5KIFEO.R8HEGONFWBLP@linux.dev> (raw)
In-Reply-To: <CAMB2axM2o+tr0hUJYWgPRO7sGg5rE5RSa_tW_sHY_oegi1_bbg@mail.gmail.com>

On Wed Sep 17, 2025 at 5:35 AM +08, Amery Hung wrote:
> On Tue, Sep 16, 2025 at 8:52 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> Currently, functions with 'union' arguments cannot be traced with
>> fentry/fexit:
>>
>> bpftrace -e 'fentry:release_pages { exit(); }' -v
>> AST node count: 6
>> Attaching 1 probe...
>> ERROR: Error loading BPF program for fentry_vmlinux_release_pages_1.
>> Kernel error log:
>> The function release_pages arg0 type UNION is unsupported.
>> processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
>>
>> ERROR: Loading BPF object(s) failed.
>>
>> The type of the 'release_pages' argument is defined as:
>>
>> typedef union {
>>         struct page **pages;
>>         struct folio **folios;
>>         struct encoded_page **encoded_pages;
>> } release_pages_arg __attribute__ ((__transparent_union__));
>>
>> This patch relaxes the restriction by allowing function arguments of type
>> 'union' to be traced in verifier.
>>
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>> ---
>>  include/linux/bpf.h | 3 +++
>>  include/linux/btf.h | 5 +++++
>>  kernel/bpf/btf.c    | 8 +++++---
>>  3 files changed, 13 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
>> index 41f776071ff51..010ecbb798c60 100644
>> --- a/include/linux/bpf.h
>> +++ b/include/linux/bpf.h
>> @@ -1119,6 +1119,9 @@ struct bpf_prog_offload {
>>  /* The argument is signed. */
>>  #define BTF_FMODEL_SIGNED_ARG          BIT(1)
>>
>> +/* The argument is a union. */
>> +#define BTF_FMODEL_UNION_ARG           BIT(2)
>> +
>
> [...]
>
>>  struct btf_func_model {
>>         u8 ret_size;
>>         u8 ret_flags;
>> diff --git a/include/linux/btf.h b/include/linux/btf.h
>> index 9eda6b113f9b4..255f8c6bd2438 100644
>> --- a/include/linux/btf.h
>> +++ b/include/linux/btf.h
>> @@ -404,6 +404,11 @@ static inline bool btf_type_is_struct(const struct btf_type *t)
>>         return kind == BTF_KIND_STRUCT || kind == BTF_KIND_UNION;
>>  }
>>
>> +static inline bool __btf_type_is_union(const struct btf_type *t)
>> +{
>> +       return BTF_INFO_KIND(t->info) == BTF_KIND_UNION;
>> +}
>> +
>>  static inline bool __btf_type_is_struct(const struct btf_type *t)
>>  {
>>         return BTF_INFO_KIND(t->info) == BTF_KIND_STRUCT;
>> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
>> index 64739308902f7..2a85c51412bea 100644
>> --- a/kernel/bpf/btf.c
>> +++ b/kernel/bpf/btf.c
>> @@ -6762,7 +6762,7 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
>>         /* skip modifiers */
>>         while (btf_type_is_modifier(t))
>>                 t = btf_type_by_id(btf, t->type);
>> -       if (btf_type_is_small_int(t) || btf_is_any_enum(t) || __btf_type_is_struct(t))
>> +       if (btf_type_is_small_int(t) || btf_is_any_enum(t) || btf_type_is_struct(t))
>>                 /* accessing a scalar */
>>                 return true;
>>         if (!btf_type_is_ptr(t)) {
>> @@ -7334,7 +7334,7 @@ static int __get_type_size(struct btf *btf, u32 btf_id,
>>         if (btf_type_is_ptr(t))
>>                 /* kernel size of pointer. Not BPF's size of pointer*/
>>                 return sizeof(void *);
>> -       if (btf_type_is_int(t) || btf_is_any_enum(t) || __btf_type_is_struct(t))
>> +       if (btf_type_is_int(t) || btf_is_any_enum(t) || btf_type_is_struct(t))
>>                 return t->size;
>>         return -EINVAL;
>>  }
>> @@ -7347,6 +7347,8 @@ static u8 __get_type_fmodel_flags(const struct btf_type *t)
>>                 flags |= BTF_FMODEL_STRUCT_ARG;
>
> Might be nit-picking but the handling of union arguments is identical
> to struct, so maybe we don't need to introduce a new flag
> BTF_FMODEL_UNION_ARG just for this. Changing __btf_type_is_struct() to
> btf_type_is_struct() here should also work.

Correct. It should work with such changing.

However, it would be more readable to introduce the new flag as the flag
indicates the argument is a 'union' instead of a 'struct'.

>
> Otherwise, the set looks good to me.
>
> Reviewed-by: Amery Hung <ameryhung@gmail.com>

Thank you for your review.

Thanks,
Leon

[...]

  reply	other threads:[~2025-09-17 12:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 15:52 [PATCH bpf-next v2 0/3] bpf: Allow union argument in trampoline based programs Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 1/3] " Leon Hwang
2025-09-16 21:35   ` Amery Hung
2025-09-17 12:40     ` Leon Hwang [this message]
2025-09-17 18:13       ` Alexei Starovoitov
2025-09-18  1:47         ` Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 2/3] bpf, x64: Add union argument support in trampoline Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add union argument tests using fexit programs Leon Hwang
2025-09-18 16:09   ` Tao Chen
2025-09-19  1:47     ` Leon Hwang
2025-09-19  1:53       ` Alexei Starovoitov
2025-09-19  2:01         ` 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=DCV2ZG5KIFEO.R8HEGONFWBLP@linux.dev \
    --to=leon.hwang@linux.dev \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cheick.traore@foss.st.com \
    --cc=chen.dylane@linux.dev \
    --cc=daniel@iogearbox.net \
    --cc=davidzalman.101@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=kernel-patches-bot@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=menglong8.dong@gmail.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=puranjay@kernel.org \
    --cc=song@kernel.org \
    --cc=yatsenko@meta.com \
    --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;
as well as URLs for NNTP newsgroup(s).