public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Arnaldo Carvalho de Melo" <acme@kernel.org>,
	martin.lau@linux.dev, bpf <bpf@vger.kernel.org>,
	clang-built-linux <llvm@lists.linux.dev>,
	"Tomasz Paweł Gajc" <tpgxyz@gmail.com>,
	"Masami Hiramatsu" <mhiramat@kernel.org>
Subject: Re: FAILED: load BTF from vmlinux: Invalid argument
Date: Fri, 4 Aug 2023 17:10:16 +0900	[thread overview]
Message-ID: <20230804171016.5676b193723d400dec062f5f@kernel.org> (raw)
In-Reply-To: <CAKwvOd=w3PFMDyZ1WL1DDx0Gyt-+sh7hYP_+8b9zEFu3uZpVXQ@mail.gmail.com>

Hi Nick,

On Thu, 3 Aug 2023 13:50:02 -0700
Nick Desaulniers <ndesaulniers@google.com> wrote:

> On Thu, Aug 3, 2023 at 1:39 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > Em Thu, Aug 03, 2023 at 11:02:46AM -0700, Nick Desaulniers escreveu:
> > > Hi Martin (and BTF/BPF team),
> > > I've observed 2 user reports with the error from the subject of this email.
> > > https://github.com/ClangBuiltLinux/linux/issues/1825
> > > https://bbs.archlinux.org/viewtopic.php?id=284177
> > >
> > > Any chance you could take a look at these reports and help us figure
> > > out what's going wrong here?  Nathan and I haven't been able to
> > > reproduce, but this seems to be affecting OpenMandriva (and Tomasz).
> > >
> > > Sounds like perhaps llvm-objcopy vs gnu objcopy might be a relevant detail?
> >
> > Masami had a problem with new versions of compilers that was solved
> > with:
> >
> > ------------------------ 8< --------------------------------------------
> > > To check that please tweak:
> > >
> > > ⬢[acme@toolbox perf-tools-next]$ grep DWARF ../build/v6.2-rc5+/.config
> > > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
> > > # CONFIG_DEBUG_INFO_DWARF4 is not set
> > > # CONFIG_DEBUG_INFO_DWARF5 is not set
> > > ⬢[acme@toolbox perf-tools-next]$
> > >
> > > i.e. disable CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT and enable
> > > CONFIG_DEBUG_INFO_DWARF4.
> >
> > Hm, with CONFIG_DEBUG_INFO_DWARF4, no warning were shown.
> 
> Downgrading from the now-6-year-old DWARFv5 to now-13-year-old DWARFv4
> is not what I'd consider a fix. Someday we can move to
> DWARFv5...someday...

Actually, even with DWARFv5, if I use newer clang, pahole succeded to make
BTF info. So it may depend on compiler version too.

> 
> What you describe sounds like build success, but reduction in debug info.
> 
> The reports I'm referring to seem to result in a build failure.

Yeah, it seems a different issue. I could build it at least.

Thank you,

> 
> >
> >   LD      .tmp_vmlinux.btf
> >   BTF     .btf.vmlinux.bin.o
> >   LD      .tmp_vmlinux.kallsyms1
> >
> > And
> >
> > / # strings /sys/kernel/btf/vmlinux | wc -l
> > 89921
> > / # strings /sys/kernel/btf/vmlinux | grep -w kfree
> > kfree
> >
> > It seems the BTF is correctly generated. (with DWARF5, the number of symbols
> > are about 30000.)
> 
> 
> 
> -- 
> Thanks,
> ~Nick Desaulniers


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      parent reply	other threads:[~2023-08-04  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 18:02 FAILED: load BTF from vmlinux: Invalid argument Nick Desaulniers
2023-08-03 20:39 ` Arnaldo Carvalho de Melo
2023-08-03 20:50   ` Nick Desaulniers
2023-08-03 22:10     ` Alan Maguire
2023-08-04 16:11       ` Nick Desaulniers
2023-08-04 16:41         ` Arnaldo Carvalho de Melo
2023-08-04 22:03         ` Alan Maguire
2023-08-05 15:42           ` Jiri Olsa
2023-08-07 16:05             ` Nick Desaulniers
2023-08-04  8:10     ` Masami Hiramatsu [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=20230804171016.5676b193723d400dec062f5f@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=ndesaulniers@google.com \
    --cc=tpgxyz@gmail.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