From: Nathan Chancellor <nathan@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Brian Cain <bcain@quicinc.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Yujie Liu <yujie.liu@intel.com>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-hexagon@vger.kernel.org, dwarves@vger.kernel.org,
Mark Wielaard <mark@klomp.org>
Subject: Re: [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault LLVM_OBJCOPY="llvm-objcopy" pahole -J --btf_gen_floats -j --lang_exclude=rust --skip_encoding_btf_inconsistent_proto --btf_gen_optimized --btf_base vmlinux drivers/misc/eeprom/at24.ko
Date: Wed, 3 Jan 2024 16:55:43 -0700 [thread overview]
Message-ID: <20240103235543.GA696229@dev-arch.thelio-3990X> (raw)
In-Reply-To: <f6moe6xstxuj2wrnqftc2w7kx4yrnjyoqnigxprvnv4ymtgre6@6ioujgedt72e>
On Wed, Jan 03, 2024 at 05:03:17PM -0500, Kent Overstreet wrote:
> On Wed, Jan 03, 2024 at 08:20:10AM -0800, Nick Desaulniers wrote:
> > On Tue, Jan 2, 2024 at 9:53 AM Mark Wielaard <mark@klomp.org> wrote:
> > >
> > > This seems to need Qualcomm to upstream support for this processor
> > > type to bintuils and elfutils.
> >
> > Probably should disable BTF for hexagon until then.
>
> Do we want to include a patch for that in the header cleanup tree?
This issue is reproducible on mainline so I don't think there needs to
be a patch for this in the header cleanup tree.
As for the patch, I assume it would look something like this?
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 4405f81248fb..1b939f5583eb 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -378,6 +378,8 @@ config DEBUG_INFO_BTF
depends on !GCC_PLUGIN_RANDSTRUCT || COMPILE_TEST
depends on BPF_SYSCALL
depends on !DEBUG_INFO_DWARF5 || PAHOLE_VERSION >= 121
+ # pahole uses elfutils, which does not have support for Hexagon relocations
+ depends on !HEXAGON
help
Generate deduplicated BTF type information from DWARF debug info.
Turning this on expects presence of pahole tool, which will convert
next prev parent reply other threads:[~2024-01-03 23:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 13:40 [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault LLVM_OBJCOPY="llvm-objcopy" pahole -J --btf_gen_floats -j --lang_exclude=rust --skip_encoding_btf_inconsistent_proto --btf_gen_optimized --btf_base vmlinux drivers/misc/eeprom/at24.ko kernel test robot
2023-12-19 20:53 ` Kent Overstreet
2023-12-19 20:58 ` Nick Desaulniers
2023-12-19 21:04 ` Kent Overstreet
2023-12-19 21:04 ` Nathan Chancellor
2023-12-19 21:12 ` [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault LLVM_OBJCOPY="llvm-objcopy" pahole -J --btf_gen_floats -j --lang_exclude=rust --skip_encoding_btf_inconsistent_proto --btf_gen_optimized --btf_base vmlinux drivers/misc/eep Brian Cain
2023-12-20 7:24 ` [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault LLVM_OBJCOPY="llvm-objcopy" pahole -J --btf_gen_floats -j --lang_exclude=rust --skip_encoding_btf_inconsistent_proto --btf_gen_optimized --btf_base vmlinux drivers/misc/eeprom/at24.ko Yujie Liu
2023-12-27 22:43 ` Nathan Chancellor
2023-12-28 14:21 ` Arnaldo Carvalho de Melo
2023-12-28 17:34 ` Nathan Chancellor
2024-01-02 16:30 ` Arnaldo Carvalho de Melo
2024-01-02 17:53 ` Mark Wielaard
2024-01-03 16:20 ` Nick Desaulniers
2024-01-03 22:03 ` Kent Overstreet
2024-01-03 23:55 ` Nathan Chancellor [this message]
2024-01-04 15:10 ` [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault LLVM_OBJCOPY="llvm-objcopy" pahole -J --btf_gen_floats -j --lang_exclude=rust --skip_encoding_btf_inconsistent_proto --btf_gen_optimized --btf_base vmlinux drivers/misc/eep Brian Cain
2024-01-03 17:25 ` Brian Cain
2024-01-03 20:45 ` Arnaldo Carvalho de Melo
2024-02-09 13:34 ` Mark Wielaard
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=20240103235543.GA696229@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=acme@kernel.org \
--cc=bcain@quicinc.com \
--cc=dwarves@vger.kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-hexagon@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mark@klomp.org \
--cc=ndesaulniers@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yujie.liu@intel.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