BPF List
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Quentin Monnet <qmo@kernel.org>,
	bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>,
	Cupertino Miranda <cupertino.miranda@oracle.com>,
	David Faust <david.faust@oracle.com>,
	Ian Rogers <irogers@google.com>,
	"Jose E . Marchesi" <jose.marchesi@oracle.com>,
	Vineet Gupta <vineet.gupta@linux.dev>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH bpf-next v2 4/8] bpftool: Skip __bpf_relocatable on verifier-rewritten context types
Date: Tue, 27 Oct 2026 11:17:59 -0700	[thread overview]
Message-ID: <5718c42b-6cc5-4816-9b67-2a22ddd7f416@linux.dev> (raw)
In-Reply-To: <CAEf4Bza2KV8ZbV2eeGyNabErZ43gY+md4WP6N7XPVL0_dw-mAA@mail.gmail.com>

On 10/27/26 11:06 AM, Andrii Nakryiko wrote:
> On Fri, Oct 23, 2026 at 3:27 PM Ihor Solodrai <ihor.solodrai@linux.dev> wrote:
>>
>> 
>> [...]
>> +
>> +/*
>> + * Anonymous records within types that need static offsets must not start
>> + * CO-RE access chains. Named records, typedefs and pointer targets are
>> + * separate types.
>> + */
>> +static void btf_c_mark_no_pai(const struct btf *btf, __u32 id, unsigned long *no_pai)
> 
> mark_static_offset to keep terminology consistent?
> 
>> +{
>> +       const struct btf_type *t = btf__type_by_id(btf, id);
>> +       const struct btf_member *m = btf_members(t);
>> +       __u32 i;
>> +
>> +       __set_bit(id, no_pai);
>> +       for (i = 0; i < btf_vlen(t); i++, m++) {
>> +               const struct btf_type *mt;
>> +               __u32 mid = m->type;
>> +
>> +               mt = btf__type_by_id(btf, mid);
>> +               while (btf_is_array(mt) || btf_is_mod(mt)) {
>> +                       mid = btf_is_array(mt) ? btf_array(mt)->type : mt->type;
>> +                       mt = btf__type_by_id(btf, mid);
>> +               }
>> +               if (btf_is_composite(mt) && !mt->name_off && !test_bit(mid, no_pai))
>> +                       btf_c_mark_no_pai(btf, mid, no_pai);
>> +       }
>> +}
>> +
>>  static int btf_c_annotate_records(struct btf *btf)
>>  {
>>         __u32 i, cnt = btf__type_cnt(btf);
>> +       unsigned long *no_pai;
>>         int err;
>>
>> +       no_pai = bitmap_zalloc(cnt);
> 
> this will cause problems for github mirror that won't have access to
> linux-internal include/linux/bitmap.h, 

Good point, haven't thought of that.


> ...I'd just open-code a simple
> bitmap or use bool array for simplicity, memory usage increase doesn't
> really matter here
> 
>> +       if (!no_pai)
>> +               return -ENOMEM;
>> +
>> +       for (i = 1; i < cnt; i++) {
>> +               if (btf_c_needs_static_offset(btf, btf__type_by_id(btf, i)))
>> +                       btf_c_mark_no_pai(btf, i, no_pai);
>> +       }
>> +
>>         for (i = 1; i < cnt; i++) {
>>                 const struct btf_type *t = btf__type_by_id(btf, i);
>>
>>                 if (!btf_is_composite(t))
>>                         continue;
>> +               if (test_bit(i, no_pai))
>> +                       continue;
>>                 err = btf__add_decl_attr(btf, "__bpf_relocatable", i, -1);
>>                 if (err < 0)
>> -                       return err;
>> +                       goto out;
>>         }
>>
>> -       return 0;
>> +       err = 0;
>> +out:
>> +       bitmap_free(no_pai);
>> +       return err;
>>  }
>>
>>  static int dump_btf_c(struct btf *btf,
>> --
>> 2.56.0
>>


  parent reply	other threads:[~2026-10-27 18:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 22:26 [PATCH bpf-next v2 0/8] bpftool: Per-record CO-RE attributes in the C dump Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 1/8] libbpf: Look up BTF strings without making BTF modifiable Ihor Solodrai
2026-10-23 22:39   ` sashiko-bot
2026-10-23 22:26 ` [PATCH bpf-next v2 2/8] selftests/bpf: Cover unknown BTF header-extension bytes in btf dump Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 3/8] bpftool: Apply __bpf_relocatable per record on BTF dump Ihor Solodrai
2026-10-27 18:03   ` Andrii Nakryiko
2026-10-27 18:15     ` Ihor Solodrai
2026-10-27 18:21       ` Andrii Nakryiko
2026-10-27 18:26         ` Ihor Solodrai
2026-10-27 21:25           ` Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 4/8] bpftool: Skip __bpf_relocatable on verifier-rewritten context types Ihor Solodrai
2026-10-27 18:06   ` Andrii Nakryiko
2026-10-27 18:10     ` Andrii Nakryiko
2026-10-27 18:17     ` Ihor Solodrai [this message]
2026-10-23 22:26 ` [PATCH bpf-next v2 5/8] bpftool: Emit __bpf_static_offset " Ihor Solodrai
2026-10-27 18:10   ` Andrii Nakryiko
2026-10-23 22:26 ` [PATCH bpf-next v2 6/8] selftests/bpf: Cover record attributes in bpftool BTF dumps Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 7/8] selftests/bpf: Cover context and socket accesses through vmlinux.h Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 8/8] bpftool: Document __bpf_relocatable and __bpf_static_offset Ihor Solodrai
2026-10-23 22:28 ` [PATCH bpf-next v2 0/8] bpftool: Per-record CO-RE attributes in the C dump Vineet Gupta

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=5718c42b-6cc5-4816-9b67-2a22ddd7f416@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=alan.maguire@oracle.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cupertino.miranda@oracle.com \
    --cc=daniel@iogearbox.net \
    --cc=david.faust@oracle.com \
    --cc=eddyz87@gmail.com \
    --cc=irogers@google.com \
    --cc=jose.marchesi@oracle.com \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    --cc=vineet.gupta@linux.dev \
    --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