From: Markus <M4rkusXXL@web.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: objtool segfault with ORC unwinder enabled
Date: Wed, 03 Jan 2018 18:26:19 +0100 [thread overview]
Message-ID: <2570840.NclWvBoOoG@markus> (raw)
In-Reply-To: <20180103163630.izaddrhf6w4shq2e@treble>
On Wed, Jan 03, 2018 at 17:36:30 CET Josh Poimboeuf wrote:
> On Wed, Jan 03, 2018 at 03:14:55PM +0100, Markus wrote:
> > On Wed, Jan 03, 2018 at 14:59:24 CET Josh Poimboeuf wrote:
> > > On Wed, Jan 03, 2018 at 01:22:07PM +0100, Markus wrote:
> > > > /tools/objtool/objtool orc generate --no-fp "arch/x86/kernel/irq.o"
> > > >
> > > > => segfault.
> > > >
> > > > Changing CFLAGS for objtool to O1 and starting from gdb:
> > > >
> > > > (gdb) r orc generate --no-fp "arch/x86/kernel/irq.o"
> > > > Starting program: tools/objtool/objtool orc generate --no-fp
> > > > "arch/x86/kernel/ irq.o"
> > > >
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > 0x000055555555e06c in elf_rebuild_rela_section
> > > > (sec=sec@entry=0x7ffff690d010) at elf.c:554
> > > > 554 relas[idx].r_info =
> > > > GELF_R_INFO(rela->sym->idx,
> > > > rela->
> > > >
> > > > >type);
> > > >
> > > > (gdb) bt
> > > > #0 0x000055555555e06c in elf_rebuild_rela_section
> > > > (sec=sec@entry=0x7ffff690d010) at elf.c:554
> > > > #1 0x000055555555d0aa in create_orc_sections
> > > > (file=file@entry=0x7ffffff7d740) at orc_gen.c:210
> > > > #2 0x000055555555c146 in check (_objname=<optimized out>,
> > > > _no_fp=<optimized out>, no_unreachable=<optimized out>,
> > > > orc=orc@entry=true) at check.c:1971 #3 0x000055555555811f in cmd_orc
> > > > (argc=<optimized out>, argv=0x7fffffffd8d8) at builtin-orc.c:54
> > > > #4 0x000055555555f490 in handle_internal_command
> > > > (argv=0x7fffffffd8d0,
> > > > argc=4) at objtool.c:108
> > > > #5 main (argc=4, argv=0x7fffffffd8d0) at objtool.c:131
> > > > (gdb) p rela->sym
> > > > $1 = (struct symbol *) 0x0
> > >
> > > I'm unable to recreate. Can you attach one of the .o files (like the
> > > above irq.o)?
> >
> > Sure, see attached. (From vanilla linux-4.14.11.)
>
> There's something weird with the toolchain. The object file doesn't
> have an ELF section symbol for the .irqentry.text section.
>
> Are there any special KCFLAGS being added? Can you build the object
> with V=1 to show the full gcc command line?
I have not added anything. There is no env variable set like $KCFLAGS or
$CFLAGS. (If that was the question.)
I think you mean this line from output:
gcc -Wp,-MD,arch/x86/kernel/.irq.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-
pc-linux-gnu/6.4.0/include -I./arch/x86/include -I./arch/x86/include/generated
-I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./
include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -
D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-
aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-
format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -
mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -
mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -
mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -
DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1
-DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -
DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-
sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -
Wno-frame-address -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -
Wframe-larger-than=2048 -fno-stack-protector -Wno-unused-but-set-variable -
Wno-unused-const-variable -fomit-frame-pointer -fno-var-tracking-assignments -
Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-
stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -
Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -
Iarch/x86/kernel/../include/asm/trace -DKBUILD_BASENAME='"irq"' -
DKBUILD_MODNAME='"irq"' -c -o arch/x86/kernel/.tmp_irq.o arch/x86/kernel/irq.c
The next line is the objtool that segfaults.
BR,
Markus
next prev parent reply other threads:[~2018-01-03 17:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 10:49 objtool segfault with ORC unwinder enabled Markus
2018-01-03 11:19 ` Greg Kroah-Hartman
2018-01-03 12:22 ` Markus
2018-01-03 13:59 ` Josh Poimboeuf
2018-01-03 14:14 ` Markus
2018-01-03 16:36 ` Josh Poimboeuf
2018-01-03 17:26 ` Markus [this message]
2018-01-04 15:46 ` Josh Poimboeuf
2018-01-04 16:56 ` Markus
2018-01-04 17:32 ` Josh Poimboeuf
2018-01-04 18:25 ` Markus
2018-01-10 17:14 ` Markus
2018-01-11 4:13 ` Josh Poimboeuf
2018-01-11 4:25 ` Josh Poimboeuf
2018-01-11 18:11 ` Markus
2018-01-11 18:20 ` Josh Poimboeuf
2018-01-11 18:52 ` Markus
2018-01-11 19:38 ` Josh Poimboeuf
2018-01-11 20:00 ` Markus
2018-01-11 20:19 ` Josh Poimboeuf
2018-01-03 14:14 ` Greg Kroah-Hartman
2018-01-03 14:36 ` Markus
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=2570840.NclWvBoOoG@markus \
--to=m4rkusxxl@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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.