Netdev List
 help / color / mirror / Atom feed
From: Michael Mullin <masmullin@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
	Yonghong Song <yhs@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bpftool: mmaped fields missing map structure in generated skeletons
Date: Mon, 23 May 2022 19:08:54 -0400	[thread overview]
Message-ID: <20220523230854.3hdduizw36huxvxw@jup> (raw)
In-Reply-To: <CAEf4BzY-K8UoT1HhXf=fwdWtY2fdprttUF27Zm6WwSUSRq8ycA@mail.gmail.com>

On Mon, May 23, 2022 at 03:38:03PM -0700, Andrii Nakryiko wrote:
> On Mon, May 23, 2022 at 3:19 PM Michael Mullin <masmullin@gmail.com> wrote:
> >
> > On Mon, May 23, 2022 at 03:02:31PM -0700, Andrii Nakryiko wrote:
> > > On Mon, May 23, 2022 at 1:26 PM Michael Mullin <masmullin@gmail.com> wrote:
> > > >
> > > > When generating a skeleton which has an mmaped map field, bpftool's
> > > > output is missing the map structure.  This causes a compile break when
> > > > the generated skeleton is compiled as the field belongs to the internal
> > > > struct maps, not directly to the obj.
> > > >
> > > > Signed-off-by: Michael Mullin <masmullin@gmail.com>
> > > > ---
> > > >  tools/bpf/bpftool/gen.c | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
> > > > index f158dc1c2149..b49293795ba0 100644
> > > > --- a/tools/bpf/bpftool/gen.c
> > > > +++ b/tools/bpf/bpftool/gen.c
> > > > @@ -853,7 +853,7 @@ codegen_maps_skeleton(struct bpf_object *obj, size_t map_cnt, bool mmaped)
> > > >                         i, bpf_map__name(map), i, ident);
> > > >                 /* memory-mapped internal maps */
> > > >                 if (mmaped && is_internal_mmapable_map(map, ident, sizeof(ident))) {
> > > > -                       printf("\ts->maps[%zu].mmaped = (void **)&obj->%s;\n",
> > > > +                       printf("\ts->maps[%zu].mmaped = (void **)&obj->maps.%s;\n",
> > >
> > > That's not right. maps.my_map is struct bpf_map *, but mmaped is
> > > supposed to be a blob of memory that is memory-mapped into map.
> > >
> > > Can you elaborate on how you trigger that compilation error with a
> > > small example?
> >
> > I have an a very small example on github. I have added some sed fixes to
> > my Makefile make my sample program compile.
> > https://github.com/masmullin2000/libbpf-sample/tree/main/c/simple
> >
> > https://github.com/masmullin2000/libbpf-sample/tree/02c7f945bf9027daedec04f485a320ba2df28204/c/simple
> > contains broken code.
> 
> You are missing -g when calling clang to generate debug info (DWARF
> and subsequently BTF). When BPF object file doesn't have BTF, we don't
> generate those bss/data/rodata/etc sections of the skeleton. You
> should be good just by adding -g.
> 

Thank you. By using -g, I am also unable to trigger the segfault
I was trying to fix with the patch
https://lore.kernel.org/bpf/20220523194917.igkgorco42537arb@jup/T/#u

I am not sure if there would be other ways to trigger the segfault.

> >
> > I apologize if this is an incorrect way to share external code.  I
> > haven't found the proper way to share example code from
> > kernelnewbies.org
> >
> > >
> > > >                                 i, ident);
> > > >                 }
> > > >                 i++;
> > > > --
> > > > 2.36.1
> > > >

      reply	other threads:[~2022-05-23 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 20:26 [PATCH] bpftool: mmaped fields missing map structure in generated skeletons Michael Mullin
2022-05-23 22:02 ` Andrii Nakryiko
2022-05-23 22:19   ` Michael Mullin
2022-05-23 22:38     ` Andrii Nakryiko
2022-05-23 23:08       ` Michael Mullin [this message]

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=20220523230854.3hdduizw36huxvxw@jup \
    --to=masmullin@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /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