From: Jiri Olsa <olsajiri@gmail.com>
To: "Philip Müller" <philm@manjaro.org>
Cc: bpf@vger.kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Bernhard Landauer <bernhard@manjaro.org>
Subject: Re: [kernel] 5.10.148 / 5.19.16 - pahole 1.24: BTFIDS vmlinux,FAILED: load BTF from vmlinux: Invalid argument
Date: Mon, 17 Oct 2022 23:29:40 +0200 [thread overview]
Message-ID: <Y03JRFZIeKR4sNZR@krava> (raw)
In-Reply-To: <3f82d342-1c0f-32c4-996e-cc063f872673@manjaro.org>
On Sat, Oct 15, 2022 at 06:48:03PM +0200, Philip Müller wrote:
> Hi all,
>
> I just got the following error for 5.10.148 and 5.19.16 when compiling with
> pahole 1.24 on CONFIG_DEBUG_INFO_BTF=y:
>
> BTFIDS vmlinux
> FAILED: load BTF from vmlinux: Invalid argument
> make: *** [Makefile:1168: vmlinux] Error 255
> make: *** Deleting file 'vmlinux'
>
> similar to:
> https://lore.kernel.org/bpf/20220825171620.cioobudss6ovyrkc@altlinux.org/t/
>
> For 5.19 I applied the following patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/plain/releases/5.15.66/kbuild-add-skip_encoding_btf_enum64-option-to-pahole.patch
>
> I wonder what is needed to get 5.10 kernel series compiled and if 5.19
> really doesn't support enum64.
hi,
thanks for the report, I think this is same issue as discussed in here:
https://lore.kernel.org/bpf/Y02Yv%2FubuCtVhtZk@dev-arch.thelio-3990X/
I'll send 5.10 backport and there's already fix for 5.19 on the list:
https://lore.kernel.org/bpf/20220916171234.841556-1-yakoyoku@gmail.com/
thanks
jirka
prev parent reply other threads:[~2022-10-17 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 16:48 [kernel] 5.10.148 / 5.19.16 - pahole 1.24: BTFIDS vmlinux,FAILED: load BTF from vmlinux: Invalid argument Philip Müller
2022-10-15 18:25 ` Philip Müller
2022-10-15 18:33 ` Martin Rodriguez Reboredo
2022-10-17 21:29 ` Jiri Olsa [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=Y03JRFZIeKR4sNZR@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bernhard@manjaro.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=philm@manjaro.org \
--cc=yakoyoku@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