From: Dominique Martinet <asmadeus@codewreck.org>
To: dwarves@vger.kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: pahole split BTF support broken on 32bit builds?
Date: Sun, 10 Jul 2022 22:43:42 +0900 [thread overview]
Message-ID: <YsrXjggSxfe2U7Oz@codewreck.org> (raw)
Hi Arnaldo,
I noticed nixos had to disable BTF for 5.15+ builds -- split BTF for
modules got in 5.11 and that's the first kernel after this so it matches
up.
I could reproduce by just building any kernel with ARCH=i386 and using a
32bit pahole
$ LD_LIBRARY_PATH=/tmp/pahole/build /tmp/pahole/build/pahole -J --btf_base vmlinux arch/x86/crypto/aesni-intel.ko
Failed to parse base BTF 'vmlinux': -22
$ file /tmp/pahole/build/pahole
/tmp/pahole/build/pahole: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /nix/store/pp1yzf2flqnjm02jnjcgxhx015bhmi9j-glibc-2.34-210/lib/ld-linux.so.2, for GNU/Linux 2.6.32, with debug_info, not stripped
(64bit pahole works with the same input, and interestingly the 32bit
pahole works with a 64bit kernel/modules -- I can reproduce on either
5.15 or current master as long as it's built with ARCH=i686 though)
If cross-compiling pahole to i686 is a pain the issue apparently is
reproductible with native armhf builds as well according to comments on
the nixos PR:
https://github.com/NixOS/nixpkgs/pull/178256
I'm not attaching a config, a minimal .config with just BTF and module
BTF was enough for me (allnoconfig adjusted to get these)
Please let me know if you need any more information,
--
Dominique
next reply other threads:[~2022-07-10 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 13:43 Dominique Martinet [this message]
2022-07-11 1:28 ` pahole split BTF support broken on 32bit builds? Dominique Martinet
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=YsrXjggSxfe2U7Oz@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=acme@kernel.org \
--cc=dwarves@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.