From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Andrii Nakryiko <andrii@kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>
Subject: Re: [linux-next:master 754/1391] /bin/bash: line 1: 50431 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/pcmcia/pcmcia_core.ko
Date: Fri, 14 Jul 2023 10:53:11 -0300 [thread overview]
Message-ID: <ZLFTR+E1nQVtFbbB@kernel.org> (raw)
In-Reply-To: <CAEf4BzaWmYcJTLc5837wA8T4KOWcQaxgh6LpYR53kT-8HoQDSQ@mail.gmail.com>
Em Tue, Jul 11, 2023 at 03:20:43PM -0700, Andrii Nakryiko escreveu:
> On Tue, Jul 11, 2023 at 6:52 AM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 8e4b7f2f3d6071665b1dfd70786229c8a5d6c256
> > commit: c628747cc8800cf6d33d09f7f42c8b6f91e64dc7 [754/1391] libbpf: only reset sec_def handler when necessary
> > config: arm-randconfig-r032-20230710 (https://download.01.org/0day-ci/archive/20230711/202307112158.3RFyuSZJ-lkp@intel.com/config)
> > compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
> > reproduce: (https://download.01.org/0day-ci/archive/20230711/202307112158.3RFyuSZJ-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/202307112158.3RFyuSZJ-lkp@intel.com/
> >
> > Note: the linux-next/master HEAD 8e4b7f2f3d6071665b1dfd70786229c8a5d6c256 builds fine.
> > It may have been fixed somewhere.
> >
> > All errors (new ones prefixed by >>):
> >
> > die__process_unit: DW_TAG_subrange_type (0x21) @ <0x14a5b> not handled!
> > die__process_unit: tag not supported 0x21 (subrange_type)!
> > die__process_unit: DW_TAG_subrange_type (0x21) @ <0x1e457> not handled!
> > die__create_new_array: DW_TAG_union_type (0x17) @ <0x14a70> not handled!
> > die__process_class: DW_TAG_compile_unit (0x11) @ <0x1e4bc> not handled!
> > die__process_class: tag not supported 0x11 (compile_unit)!
> > >> /bin/bash: line 1: 50431 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/pcmcia/pcmcia_core.ko
> >
>
> Cc'ing Arnaldo and Eduard. I don't know if it's the same as [0], but
> just in case please take a look.
>
> [0] https://lore.kernel.org/bpf/20230710200002.ca4okot5rrvewqvb@altlinux.org/
I'll try to reproduce, but if the vmlinux and pcmcia_core.ko files that
were produced in this test run could be made available, that would speed
up things.
Otherwise I'll try to use https://download.01.org/0day-ci/archive/20230711/202307112158.3RFyuSZJ-lkp@intel.com/reproduce
Thise are not types that usually appear in C, so perhaps the
--lang_exclude=rust isn't working for some reason, i.e. looking at the
DW_TAG_compile_unit to se the DW_AT_language.
Processing arrays and getting a union type? Interesting :-)
- Arnaldo
prev parent reply other threads:[~2023-07-14 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 13:51 [linux-next:master 754/1391] /bin/bash: line 1: 50431 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/pcmcia/pcmcia_core.ko kernel test robot
2023-07-11 22:20 ` Andrii Nakryiko
2023-07-14 13:53 ` Arnaldo Carvalho de Melo [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=ZLFTR+E1nQVtFbbB@kernel.org \
--to=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=eddyz87@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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).