From: "Érico Rolim" <erico.erc@gmail.com>
To: dwarves@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Segfault in pahole 1.18 when building kernel 5.9.1 for arm64
Date: Sun, 18 Oct 2020 20:18:33 -0300 [thread overview]
Message-ID: <CAFDeuWM7D-Upi84-JovKa3g8Y_4fjv65jND3--e9u-tER3WmVA@mail.gmail.com> (raw)
Hi!
I'm trying to build kernel 5.9.1 for arm64, and my dotconfig has
`CONFIG_DEBUG_INFO_BTF=y`, which requires pahole for building. However, pahole
version 1.18 segfaults during the build, as can be seen below:
PAHOLE: Error: Found symbol of zero size when encoding btf (sym:
'__kvm_nvhe_arm64_ssbd_callback_required', cu:
'arch/arm64/kernel/cpu_errata.c').
PAHOLE: Error: Use '-j' or '--force' to ignore such symbols and force
emit the btf.
scripts/link-vmlinux.sh: line 141: 43837 Segmentation fault
LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} -J ${1}
LD .tmp_vmlinux.kallsyms1
KSYM .tmp_vmlinux.kallsyms1.o
LD .tmp_vmlinux.kallsyms2
KSYM .tmp_vmlinux.kallsyms2.o
LD vmlinux
BTFIDS vmlinux
FAILED: load BTF from vmlinux: Unknown error -2make: ***
[Makefile:1162: vmlinux] Error 255
It is possible to force the build to continue if
LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} -J ${1}
in scripts/link-vmlinux.sh is changed to
LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} -J --btf_encode_force ${1}
The suggested `-j` or `--force` flags don't exist, since they were removed in
[1]. I believe `--btf_encode_force` should be suggested instead.
It should be noted that the same build, but with pahole version 1.17, works
without issue, so I think this is either a regression in pahole or the script
will need to be changed for newer versions of pahole.
- [1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/pahole.c?h=v1.18&id=1abc001417b579b86a9b27ff88c9095d8f498a46
Thanks,
Érico
next reply other threads:[~2020-10-18 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 23:18 Érico Rolim [this message]
2020-10-20 9:01 ` Segfault in pahole 1.18 when building kernel 5.9.1 for arm64 Jiri Slaby
2020-10-20 12:20 ` Arnaldo Carvalho de Melo
2020-10-20 17:04 ` Hao Luo
2020-10-20 17:10 ` Andrii Nakryiko
2020-10-20 17:18 ` Hao Luo
2020-10-20 18:14 ` Arnaldo Carvalho de Melo
2020-10-20 19:02 ` Arnaldo Carvalho de Melo
2020-10-21 6:22 ` Jiri Slaby
2020-10-21 11:29 ` Arnaldo Carvalho de Melo
2020-10-21 15:53 ` Andrii Nakryiko
2020-10-21 16:26 ` Arnaldo Carvalho de Melo
2020-10-20 17:15 ` Andrii Nakryiko
2020-10-21 5:52 ` Jiri Slaby
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=CAFDeuWM7D-Upi84-JovKa3g8Y_4fjv65jND3--e9u-tER3WmVA@mail.gmail.com \
--to=erico.erc@gmail.com \
--cc=dwarves@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).