From: Nathan Chancellor <nathan@kernel.org>
To: Yujie Liu <yujie.liu@intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Brian Cain <bcain@quicinc.com>,
linux-hexagon@vger.kernel.org, dwarves@vger.kernel.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, 27 Dec 2023 15:43:38 -0700 [thread overview]
Message-ID: <20231227224338.GA267659@dev-arch.thelio-3990X> (raw)
In-Reply-To: <ZYKWxl9oQXODIoNe@yujie-X299>
+ Arnaldo and dwarves list
On Wed, Dec 20, 2023 at 03:24:54PM +0800, Yujie Liu wrote:
> On Tue, Dec 19, 2023 at 02:04:54PM -0700, Nathan Chancellor wrote:
> > On Tue, Dec 19, 2023 at 12:58:28PM -0800, Nick Desaulniers wrote:
> > > On Tue, Dec 19, 2023 at 12:54 PM Kent Overstreet
> > > <kent.overstreet@linux.dev> wrote:
> > > >
> > > > On Tue, Dec 19, 2023 at 09:40:09PM +0800, kernel test robot wrote:
> > > > > tree: https://evilpiepirate.org/git/bcachefs.git header_cleanup
> > > > > head: 89188fceb7a49e3c4b0578d86f6f6e647f202821
> > > > > commit: 1db61740aeb7d6b1c7bfb2a98708a65a6679d068 [21/51] locking/seqlock: Split out seqlock_types.h
> > > > > config: hexagon-randconfig-r005-20220913 (https://download.01.org/0day-ci/archive/20231219/202312192107.wMIKiZWw-lkp@intel.com/config)
> > > > > compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> > > > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231219/202312192107.wMIKiZWw-lkp@intel.com/reproduce)
> > > > >
> > > > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > > > the same patch/commit), kindly add following tags
> > > > > | Reported-by: kernel test robot <lkp@intel.com>
> > > > > | Closes: https://lore.kernel.org/oe-kbuild-all/202312192107.wMIKiZWw-lkp@intel.com/
> > > > >
> > > > > All errors (new ones prefixed by >>):
> > > > >
> > > > > die__process_unit: DW_TAG_member (0xd) @ <0xc689> not handled!
> > > > > die__process_unit: tag not supported 0xd (member)!
> > > > > die__process_function: DW_TAG_compile_unit (0x11) @ <0xc697> not handled!
> > > > > die__process_function: tag not supported 0x11 (compile_unit)!
> > > > > die__process_function: DW_TAG_member (0xd) @ <0xc6db> not handled!
> > > > > die__process_function: DW_TAG_compile_unit (0x11) @ <0xc6e5> not handled!
> > > > > die__process_class: DW_TAG_compile_unit (0x11) @ <0xc778> not handled!
> > > > > namespace__recode_dwarf_types: couldn't find 0xc689 type for 0xc66b (member)!
> > > > > namespace__recode_dwarf_types: couldn't find 0xc638 type for 0xc674 (member)!
> > > > > namespace__recode_dwarf_types: couldn't find 0xc638 type for 0xc67e (member)!
> > > > > >> /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
> > > >
> > > > Not sure how likely a header cleanup is to cause a segfault in
> > > > llvm-objcopy and I don't have the toolchain to repro this - could
> > > > hexagon people take a look?
> >
> > For what it's worth in case you were not aware, I provide copies of LLVM
> > on kernel.org that can be installed in some prefix and invoked with
> > LLVM=<prefix>/bin/, which can make reproducing reports such as these
> > relatively easy.
> >
> > https://mirrors.edge.kernel.org/pub/tools/llvm/
> >
> > > Is it a segfault in llvm-objcopy, or pahole?
> >
> > Should be pahole. I have not been able to reproduce these crashes in
> > pahole v1.25 in the past when they come up every so often. 0day folks,
> > what version of pahole are you testing with?
>
> We clone pahole source code from [1] and build it on the master branch.
> The current head is commit c129fa757948 which is newer than v1.25.
>
> c129fa757948 ("pahole: Add --btf_features_strict to reject unknown BTF features")
>
> [1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git
Thanks for that additional information but I can reproduce this at v1.25
as well, I just tried:
$ git fetch https://evilpiepirate.org/git/bcachefs.git 1db61740aeb7d6b1c7bfb2a98708a65a6679d068
$ git reset --hard FETCH_HEAD
$ curl -LSso .config https://download.01.org/0day-ci/archive/20231219/202312192107.wMIKiZWw-lkp@intel.com/config
$ curl -LSs https://mirrors.edge.kernel.org/pub/tools/llvm/files/llvm-16.0.6-x86_64.tar.xz | tar -xJf -
$ make -skj"$(nproc)" ARCH=hexagon LLVM=$PWD/llvm-16.0.6-x86_64/bin/ olddefconfig all
...
die__process: got compile_unit unexpected tag after DW_TAG_compile_unit!
die__create_new_enumeration: DW_TAG_array_type (0x1) @ <0x120b1> not handled!
die__create_new_enumeration: DW_TAG_pointer_type (0xf) @ <0x120b7> not handled!
die__process_unit: DW_TAG_member (0xd) @ <0x3669> not handled!
die__process_unit: tag not supported 0xd (member)!
die__process: got compile_unit unexpected tag after DW_TAG_compile_unit!
die__process_unit: DW_TAG_member (0xd) @ <0x3650> not handled!
die__process_unit: tag not supported 0xd (member)!
die__process: got compile_unit unexpected tag after DW_TAG_compile_unit!
die__create_new_enumeration: DW_TAG_array_type (0x1) @ <0x9cb5> not handled!
die__create_new_enumeration: DW_TAG_pointer_type (0xf) @ <0x9cbb> not handled!
die__process_unit: DW_TAG_enumerator (0x28) @ <0x705a> not handled!
die__process_unit: tag not supported 0x28 (enumerator)!
...
I do not get a segfault personally but there are definitely a lot of
errors from pahole at the end. Arnaldo, is pahole not handling something
that it should with regards to clang's debug info?
Cheers,
Nathan
next parent reply other threads:[~2023-12-27 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202312192107.wMIKiZWw-lkp@intel.com>
[not found] ` <20231219205348.wvvxyicaatmljxm2@moria.home.lan>
[not found] ` <CAKwvOdmrvwdbFrtzsOjoLJJZ1pDZOBWBiEb=Mx5bCHuKU2wPzQ@mail.gmail.com>
[not found] ` <20231219210454.GA540439@dev-arch.thelio-3990X>
[not found] ` <ZYKWxl9oQXODIoNe@yujie-X299>
2023-12-27 22:43 ` Nathan Chancellor [this message]
2023-12-28 14:21 ` [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 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
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=20231227224338.GA267659@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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).