From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Markus <M4rkusXXL@web.de>
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: Thu, 11 Jan 2018 12:20:57 -0600 [thread overview]
Message-ID: <20180111182057.psy4plwhfsetkuzc@treble> (raw)
In-Reply-To: <1574206.L1kTMSv4rA@markus>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
On Thu, Jan 11, 2018 at 07:11:03PM +0100, Markus wrote:
> On Thursday, 11 January 2018 05:25:51 CET Josh Poimboeuf wrote:
> > On Wed, Jan 10, 2018 at 10:13:00PM -0600, Josh Poimboeuf wrote:
> > > On Wed, Jan 10, 2018 at 06:14:56PM +0100, Markus wrote:
> > > > On Thursday, 4 January 2018 19:25:12 CET Markus wrote:
> > > > > On Thursday, 4 January 2018 18:32:03 CET Josh Poimboeuf wrote:
> > > > > > On Thu, Jan 04, 2018 at 05:56:30PM +0100, Markus wrote:
> > > > > > > On Thursday, 4 January 2018 16:46:13 CET Josh Poimboeuf wrote:
> > > > > > > > I don't see anything unusual there. Are there any Gentoo
> > > > > > > > patches
> > > > > > > > against either the kernel or GCC which would strip unused
> > > > > > > > symbols?
> > > > > > >
> > > > > > > The kernel is the vanilla kernel. (4.14.11 and also 4.15-rc6)
> > > > > > > Its not a gentoo specific gcc patch. (Then every gentoo user would
> > > > > > > be
> > > > > > > affected?)
> > > > > > >
> > > > > > > But I enabled ld.gold as default linker like 5 years ago. Never
> > > > > > > had a
> > > > > > > problem with this.
> > > > > > >
> > > > > > > Is ld.gold supposed to fail here?
> > > > > > >
> > > > > > > I switched back to ld.bfd and it seems to work.
> > > > > >
> > > > > > Ah, that explains it. With CONFIG_MODVERSIONS, the linker does some
> > > > > > work after gcc, but before objtool. Can you try this patch? (Note
> > > > > > this
> > > > > > isn't the final patch, as this breaks the CONFIG_MODVERSIONS=n
> > > > > > case.)
> > > >
> > > > Any more final patch I should test?
> > >
> > > Sorry, this fell off my radar. I'll try to get a final patch soon.
> > > (But feel free to keep bugging me if I don't!)
> >
> > Ok, this should be the final patch (no description yet though). Want to
> > test it?
>
> Tried to apply to 4.14.13 and 4.15-rc7. Neither applied cleanly.
> Manually editing just breaks the build with many "open: No such file or
> directory".
>
> Dont know what went wrong. Can you maybe append patch as file?
Sure, patch is attached, based on 4.15-rc7.
--
Josh
[-- Attachment #2: objtool-gold.patch --]
[-- Type: text/plain, Size: 1603 bytes --]
diff --git a/scripts/Makefile.build b/scripts/Makefile.build
index cb8997ed0149..6f0c0c409e67 100644
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
@@ -265,12 +265,18 @@ else
objtool_args += $(call cc-ifversion, -lt, 0405, --no-unreachable)
endif
+ifdef CONFIG_MODVERSIONS
+objtool_o := $(@D)/.tmp_$(@F)
+else
+objtool_o := $(@)
+endif
+
# 'OBJECT_FILES_NON_STANDARD := y': skip objtool checking for a directory
# 'OBJECT_FILES_NON_STANDARD_foo.o := 'y': skip objtool checking for a file
# 'OBJECT_FILES_NON_STANDARD_foo.o := 'n': override directory skip for a file
cmd_objtool = $(if $(patsubst y%,, \
$(OBJECT_FILES_NON_STANDARD_$(basetarget).o)$(OBJECT_FILES_NON_STANDARD)n), \
- $(__objtool_obj) $(objtool_args) "$(@)";)
+ $(__objtool_obj) $(objtool_args) "$(objtool_o)";)
objtool_obj = $(if $(patsubst y%,, \
$(OBJECT_FILES_NON_STANDARD_$(basetarget).o)$(OBJECT_FILES_NON_STANDARD)n), \
$(__objtool_obj))
@@ -286,16 +292,16 @@ objtool_dep = $(objtool_obj) \
define rule_cc_o_c
$(call echo-cmd,checksrc) $(cmd_checksrc) \
$(call cmd_and_fixdep,cc_o_c) \
+ $(call echo-cmd,objtool) $(cmd_objtool) \
$(cmd_modversions_c) \
$(cmd_checkdoc) \
- $(call echo-cmd,objtool) $(cmd_objtool) \
$(call echo-cmd,record_mcount) $(cmd_record_mcount)
endef
define rule_as_o_S
$(call cmd_and_fixdep,as_o_S) \
- $(cmd_modversions_S) \
- $(call echo-cmd,objtool) $(cmd_objtool)
+ $(call echo-cmd,objtool) $(cmd_objtool) \
+ $(cmd_modversions_S)
endef
# List module undefined symbols (or empty line if not enabled)
next prev parent reply other threads:[~2018-01-11 18:21 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
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 [this message]
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=20180111182057.psy4plwhfsetkuzc@treble \
--to=jpoimboe@redhat.com \
--cc=M4rkusXXL@web.de \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox