bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	clm@meta.com, ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v2 03/10] bpf: Add btf_type_is_arena_ptr()
Date: Wed, 26 Aug 2026 10:28:44 -0700	[thread overview]
Message-ID: <60851aa9-9483-4fcc-9013-0679d191d001@linux.dev> (raw)
In-Reply-To: <bf7b20c25763c95f0438bd265d8a3abb1871c527882e6e7f0944be76f88d90f7@mail.kernel.org>



On 8/25/26 2:59 PM, bot+bpf-ci@kernel.org wrote:
>> bpf: Add btf_type_is_arena_ptr()
>>
>> Simplify btf_scan_type_tags() and added a new helper
>> btf_type_is_arena_ptr(). No functional change.
> This isn't a bug, but could the changelog use the imperative mood
> consistently (e.g., "Simplify ... and add ...")?  Also, could it explain
> why the helper needs external linkage, such as noting that a later patch
> calls it from verifier.c?
>
>> diff --git a/include/linux/btf.h b/include/linux/btf.h
>> index 89d5a5c4f1171..ddd0f4f32d24b 100644
>> --- a/include/linux/btf.h
>> +++ b/include/linux/btf.h
>> @@ -235,6 +235,7 @@ struct btf_record *btf_parse_fields(const struct btf *btf, const struct btf_type
>>   				    u32 field_mask, u32 value_size);
>>   int btf_check_and_fixup_fields(const struct btf *btf, struct btf_record *rec);
>>   bool btf_type_is_void(const struct btf_type *t);
>> +bool btf_type_is_arena_ptr(const struct btf *btf, const struct btf_type *t);
>>   s32 btf_find_by_name_kind(const struct btf *btf, const char *name, u8 kind);
>>   s32 bpf_find_btf_id(const char *name, u32 kind, struct btf **btf_p);
>>   struct btf *btf_get_module_btf(const struct module *module);
>> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
>> index 47d43eb983a50..280530d25886c 100644
>> --- a/kernel/bpf/btf.c
>> +++ b/kernel/bpf/btf.c
>> @@ -3523,6 +3523,22 @@ static int btf_type_tag_walk(const struct btf *btf,
>>   	return 0;
>>   }
>>
>> +bool btf_type_is_arena_ptr(const struct btf *btf, const struct btf_type *t)
>> +{
>> +	if (!btf_type_is_ptr(t))
>> +		return false;
>> +
>> +	for (t = btf_type_by_id(btf, t->type); btf_type_is_modifier(t);
>> +	     t = btf_type_by_id(btf, t->type)) {
>> +		if (!btf_type_is_type_tag(t) || btf_type_kflag(t))
>> +			continue;
>> +		if (!strcmp(__btf_name_by_offset(btf, t->name_off), "arena"))
>> +			return true;
>> +	}
>> +
>> +	return false;
>> +}
> This isn't a bug, but since btf_type_tag_walk() sits right above this and
> is still used by btf_find_kptr() and friends, could btf_type_is_arena_ptr()
> be expressed in terms of it rather than repeating the modifier/type-tag
> walk?

Okay, will have more information in commit message.

>
> [ ... ]
>
>
> ---
> 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/32899532405


  reply	other threads:[~2026-08-26 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 20:54 [PATCH bpf-next v2 00/10] bpf: Allow arena pointers in by-value returns Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 01/10] bpf: Record each half of a paired return value in verifier diagnostics Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-26 17:08     ` Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 02/10] bpf: Drop the recursion depth argument of btf_type_is_scalar_struct() Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 03/10] bpf: Add btf_type_is_arena_ptr() Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-26 17:28     ` Yonghong Song [this message]
2026-08-25 20:54 ` [PATCH bpf-next v2 04/10] bpf: Let the by-value struct walk take the kinds of member it accepts Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-26 17:39     ` Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 05/10] bpf: Report which member makes a kfunc return type unsupported Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-26 17:59     ` Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 06/10] bpf: Allow a global function to return arena pointers by value Yonghong Song
2026-08-25 21:12   ` sashiko-bot
2026-08-26 18:40     ` Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 07/10] bpf: Allow arena pointers in a by-value kfunc return Yonghong Song
2026-08-25 22:13   ` bot+bpf-ci
2026-08-26 18:57     ` Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 08/10] selftests/bpf: Check the member named for an unsupported kfunc return type Yonghong Song
2026-08-25 20:54 ` [PATCH bpf-next v2 09/10] selftests/bpf: Test global functions returning arena pointers by value Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-27  3:46     ` Yonghong Song
2026-08-25 20:55 ` [PATCH bpf-next v2 10/10] selftests/bpf: Test kfuncs " Yonghong Song
2026-08-25 21:59   ` bot+bpf-ci
2026-08-27  3:58     ` 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=60851aa9-9483-4fcc-9013-0679d191d001@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=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@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;
as well as URLs for NNTP newsgroup(s).