The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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: Wed, 10 Jan 2018 22:13:00 -0600	[thread overview]
Message-ID: <20180111041300.tr57lsn7c54ggx7c@treble> (raw)
In-Reply-To: <6019408.f4ZjTQluLH@markus>

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!)

-- 
Josh

  reply	other threads:[~2018-01-11  4:13 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 [this message]
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=20180111041300.tr57lsn7c54ggx7c@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