From: Yonghong Song <yonghong.song@linux.dev>
To: bot+bpf-ci@kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, kernel-team@fb.com, martin.lau@kernel.org,
mason@kernel.org, ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next 08/12] bpf: Record a 16-byte argument alignment in the function model
Date: Mon, 7 Sep 2026 21:28:43 -0700 [thread overview]
Message-ID: <aa959f6f-dd5b-4a7e-b34d-a3d71ecd23a7@linux.dev> (raw)
In-Reply-To: <8d16df40357e1ac7177a9e63e754fb506f348198ee3dfbad37d7c969b0f13431@mail.kernel.org>
On 9/3/26 11:09 PM, bot+bpf-ci@kernel.org wrote:
>> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
>> index 3a7eb2185c35..5b93aa97f1bc 100644
>> --- a/include/linux/bpf.h
>> +++ b/include/linux/bpf.h
>> @@ -1193,6 +1193,9 @@ struct bpf_prog_offload {
>> u32 jited_len;
>> };
>>
>> +/* Argument aligned to 16 bytes. */
>> +#define BTF_FMODEL_ALIGN16_ARG BIT(0)
>> +
>> /* The argument is signed. */
>> #define BTF_FMODEL_SIGNED_ARG BIT(1)
> [ ... ]
>
>> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
>> index 6c391449e298..f933a675b0a8 100644
>> --- a/kernel/bpf/btf.c
>> +++ b/kernel/bpf/btf.c
>> @@ -7633,6 +7633,15 @@ int btf_distill_func_proto(struct bpf_verifier_log *log,
>> }
>> m->arg_size[i] = ret;
>> m->arg_flags[i] = __get_arg_fmodel_flags(btf, &args[i], t);
>> +
>> + align16 = btf_type_align16(btf, t, 0);
>> + if (align16 < 0) {
>> + bpf_log(log, "The function %s arg%d type %s has unknown alignment.\n",
>> + tname, i, btf_type_str(t));
>> + return -EINVAL;
>> + } else if (align16) {
>> + m->arg_flags[i] |= BTF_FMODEL_ALIGN16_ARG;
>> + }
>> }
>> m->nr_args = nargs;
>> return 0;
> [ ... ]
>
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index 030fb37c22ef..461883158ffa 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -11748,6 +11748,31 @@ bool btf_struct_is_composed_of(struct bpf_verifier_env *env,
>> return btf_struct_member_walk(env, btf, t, member_kinds, 0, NULL);
>> }
>>
>> +int btf_type_align16(const struct btf *btf, const struct btf_type *t, int rec)
>> +{
>> + const struct btf_member *member;
>> + int ret;
>> + u32 i;
>> +
>> + while (btf_type_is_array(t))
>> + t = btf_type_skip_modifiers(btf, btf_array(t)->type, NULL);
>> +
>> + if (btf_type_is_int(t))
>> + return t->size > 8;
>> + if (!btf_type_is_struct(t))
>> + return 0;
>> + if (rec >= BTF_MEMBER_MAX_DEPTH)
>> + return -E2BIG;
>> +
>> + for_each_member(i, t, member) {
>> + ret = btf_type_align16(btf, btf_type_skip_modifiers(btf, member->type, NULL),
>> + rec + 1);
>> + if (ret)
>> + return ret;
>> + }
>> + return 0;
>> +}
> This isn't a bug, but btf_type_align16() looks structurally similar to
> kfunc_arg_align() further down in the same file. Both walk types with the
> same pattern: strip arrays with `while (btf_type_is_array(t))`, test for
> `btf_type_is_int(t)` with `t->size > 8`, bail on `!btf_type_is_struct(t)`,
> check `rec >= BTF_MEMBER_MAX_DEPTH`, and recurse through members via
> `btf_type_skip_modifiers(btf, member->type, NULL)`. Could the two share one
> walk, and would hiding the `rec` argument behind a wrapper keep the exported
> signature simpler, the way btf_struct_is_composed_of() wraps
> btf_struct_member_walk()?
This is for arm64 jit. I will simplify it and this patch is not necessary any more.
>
>
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
>
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/33840714551
next prev parent reply other threads:[~2026-09-08 4:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 5:09 [PATCH bpf-next 00/12] bpf: Support by-value struct and __int128 arguments Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 01/12] selftests/bpf: Add a test for an __int128 by-value argument Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 02/12] bpf: Index global function arguments by argument slot Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 03/12] bpf: Support by-value struct arguments up to 16 bytes Yonghong Song
2026-09-04 5:23 ` sashiko-bot
2026-09-08 4:17 ` Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-08 4:19 ` Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 04/12] bpf: Support __int128 as a by-value function argument Yonghong Song
2026-09-04 5:32 ` sashiko-bot
2026-09-08 4:20 ` Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-08 4:21 ` Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 05/12] bpf: Support by-value struct and __int128 kfunc arguments Yonghong Song
2026-09-04 6:18 ` sashiko-bot
2026-09-08 4:22 ` Yonghong Song
2026-09-04 6:24 ` bot+bpf-ci
2026-09-08 4:23 ` Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 06/12] bpf: Add a JIT helper for the outgoing stack of kfunc calls Yonghong Song
2026-09-04 5:25 ` sashiko-bot
2026-09-08 4:26 ` Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 07/12] bpf, x86: Place kfunc arguments per the SysV calling convention Yonghong Song
2026-09-04 5:36 ` sashiko-bot
2026-09-08 4:27 ` Yonghong Song
2026-09-04 23:58 ` Alexei Starovoitov
2026-09-06 20:15 ` Yonghong Song
2026-09-08 4:33 ` Alexei Starovoitov
2026-09-08 5:02 ` Yonghong Song
2026-09-08 5:10 ` Yonghong Song
2026-09-08 15:24 ` Alexei Starovoitov
2026-09-08 18:43 ` Yonghong Song
2026-09-09 1:59 ` Alexei Starovoitov
2026-09-04 5:10 ` [PATCH bpf-next 08/12] bpf: Record a 16-byte argument alignment in the function model Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-08 4:28 ` Yonghong Song [this message]
2026-09-04 5:10 ` [PATCH bpf-next 09/12] bpf, arm64: Place kfunc arguments per AAPCS64 Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-04 5:10 ` [PATCH bpf-next 10/12] selftests/bpf: Add C tests for by-value arguments up to 16 bytes Yonghong Song
2026-09-04 5:19 ` sashiko-bot
2026-09-08 4:33 ` Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-08 4:34 ` Yonghong Song
2026-09-04 5:10 ` [PATCH bpf-next 11/12] selftests/bpf: Add inline-asm tests for by-value arguments Yonghong Song
2026-09-04 6:09 ` bot+bpf-ci
2026-09-08 4:35 ` Yonghong Song
2026-09-04 5:11 ` [PATCH bpf-next 12/12] selftests/bpf: Add tests for by-value kfunc arguments Yonghong Song
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=aa959f6f-dd5b-4a7e-b34d-a3d71ecd23a7@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=mason@kernel.org \
/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