BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>, qmo@kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, 	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, 	kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, 	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] libbpf: add option to force-anonymize nested structs for BTF dump
Date: Tue, 16 Dec 2025 11:46:15 -0800	[thread overview]
Message-ID: <9a096b2a16d552031a12f3f4f5a2c725212df5e6.camel@gmail.com> (raw)
In-Reply-To: <d5a578c01f8a2d4d95ca16e0a9ee5b9bfce1c30e.camel@gmail.com>

On Tue, 2025-12-16 at 11:00 -0800, Eduard Zingerman wrote:
> On Tue, 2025-12-16 at 17:18 +0000, Alan Maguire wrote:
>
> [...]
>
> > @@ -1460,10 +1466,16 @@ static void btf_dump_emit_type_chain(struct btf_dump *d,
> >  		case BTF_KIND_UNION:
> >  			btf_dump_emit_mods(d, decls);
> >  			/* inline anonymous struct/union */
> > -			if (t->name_off == 0 && !d->skip_anon_defs)
> > +			if (t->name_off == 0 && !d->skip_anon_defs) {
> >  				btf_dump_emit_struct_def(d, id, t, lvl);
> > -			else
> > +			} else if (decls->cnt == 0 && !fname[0] && d->force_anon_struct_members) {
> > +				/* anonymize nested struct and emit it */
> > +				btf_dump_set_anon_type(d, id, true);
> > +				btf_dump_emit_struct_def(d, id, t, lvl);
> > +				btf_dump_set_anon_type(d, id, false);
>
>
> Hi Alan,
>
> I think this is a solid idea.
>
> It seems to me that with current implementation there would be a
> trouble in the following scenario:
>
>   struct foo { struct foo *ptr; };
>   struct bar {
>     struct foo;
>   }
>
> Because state for 'foo' will be anonymize == true at the moment when
> 'ptr' field is printed.
>
> Maybe pass a direct parameter to btf_dump_emit_struct_def()?

Digging a bit more into this, here are a couple of weird examples:

  $ cat ~/tmp/ms-ext-test.c
  struct foo {
    struct foo *ptr;
  };

  struct bar {
    struct foo;
  };

  struct bar root;
  $ gcc -g -c -o ~/tmp/ms-ext-test.o ~/tmp/ms-ext-test.c
  $ pahole -J ~/tmp/ms-ext-test.o
  $ bpftool btf dump file ~/tmp/ms-ext-test.o format c
  #ifndef __VMLINUX_H__
  #define __VMLINUX_H__

  #ifndef BPF_NO_PRESERVE_ACCESS_INDEX
  #pragma clang attribute push (__attribute__((preserve_access_index)), apply_to = record)
  #endif

  #ifndef __ksym
  #define __ksym __attribute__((section(".ksyms")))
  #endif

  #ifndef __weak
  #define __weak __attribute__((weak))
  #endif

  #ifndef __bpf_fastcall
  #if __has_attribute(bpf_fastcall)
  #define __bpf_fastcall __attribute__((bpf_fastcall))
  #else
  #define __bpf_fastcall
  #endif
  #endif

  struct foo {
  	struct foo *ptr;
  };


  /* BPF kfuncs */
  #ifndef BPF_NO_KFUNC_PROTOTYPES
  #endif

  #ifndef BPF_NO_PRESERVE_ACCESS_INDEX
  #pragma clang attribute pop
  #endif

  #endif /* __VMLINUX_H__ */


  $ cat ~/tmp/ms-ext-test.c
  struct foo {
    struct foo *ptr;
  };

  struct bar {
    struct foo;
    int a;
  };

  struct bar root;
  $ cgcc -fms-extensions -g -c -o ~/tmp/ms-ext-test.o ~/tmp/ms-ext-test.c
  $ pahole -J ~/tmp/ms-ext-test.o
  $ tools/bpf/bpftool/bpftool btf dump file ~/tmp/ms-ext-test.o format c
  #ifndef __VMLINUX_H__
  #define __VMLINUX_H__

  #ifndef BPF_NO_PRESERVE_ACCESS_INDEX
  #pragma clang attribute push (__attribute__((preserve_access_index)), apply_to = record)
  #endif

  #ifndef __ksym
  #define __ksym __attribute__((section(".ksyms")))
  #endif

  #ifndef __weak
  #define __weak __attribute__((weak))
  #endif

  #ifndef __bpf_fastcall
  #if __has_attribute(bpf_fastcall)
  #define __bpf_fastcall __attribute__((bpf_fastcall))
  #else
  #define __bpf_fastcall
  #endif
  #endif

  struct foo {
  	struct foo *ptr;
  };

  struct bar {
  	struct  {
  		struct  *ptr;
  	};
  	int a;
  };


  /* BPF kfuncs */
  #ifndef BPF_NO_KFUNC_PROTOTYPES
  #endif

  #ifndef BPF_NO_PRESERVE_ACCESS_INDEX
  #pragma clang attribute pop
  #endif

  #endif /* __VMLINUX_H__ */

  parent reply	other threads:[~2025-12-16 19:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 17:18 [PATCH bpf-next 0/2] Handle -fms-extension in kernel structs Alan Maguire
2025-12-16 17:18 ` [PATCH bpf-next 1/2] libbpf: add option to force-anonymize nested structs for BTF dump Alan Maguire
2025-12-16 19:00   ` Eduard Zingerman
2025-12-16 19:08     ` Andrii Nakryiko
2025-12-16 19:46     ` Eduard Zingerman [this message]
2025-12-17 16:06       ` Alan Maguire
2025-12-17 16:12         ` Alexei Starovoitov
2025-12-17 17:06           ` Andrii Nakryiko
2025-12-17 17:33             ` Alan Maguire
2025-12-17 17:52               ` Alexei Starovoitov
2025-12-17 18:41                 ` Alan Maguire
2025-12-17 19:34                   ` Eduard Zingerman
2025-12-17 19:35                     ` Eduard Zingerman
2025-12-17 20:50                       ` Alan Maguire
2025-12-17 21:02                         ` Andrii Nakryiko
2025-12-17 21:27                           ` Alexei Starovoitov
2025-12-17 22:34                             ` Eduard Zingerman
2025-12-17 22:47                               ` Eduard Zingerman
2025-12-17 23:34                                 ` Alexei Starovoitov
2025-12-18  0:19                                   ` Eduard Zingerman
2025-12-18  0:39                                     ` Alexei Starovoitov
2025-12-18  0:50                                       ` Eduard Zingerman
2025-12-17 23:52                             ` Andrii Nakryiko
2025-12-18  0:49                               ` Eduard Zingerman
2025-12-17 17:10         ` Andrii Nakryiko
2025-12-16 17:18 ` [PATCH bpf-next 2/2] bpftool: force-anonymize structs to avoid need for -fms-extension Alan Maguire
2025-12-16 19:20 ` [PATCH bpf-next 0/2] Handle -fms-extension in kernel structs Song Liu

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=9a096b2a16d552031a12f3f4f5a2c725212df5e6.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --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