From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus <M4rkusXXL@web.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: objtool segfault with ORC unwinder enabled
Date: Wed, 3 Jan 2018 15:14:01 +0100 [thread overview]
Message-ID: <20180103141401.GC12918@kroah.com> (raw)
In-Reply-To: <1954665.Z2ZbY5be2g@markus>
On Wed, Jan 03, 2018 at 01:22:07PM +0100, Markus wrote:
> On Wed, Jan 03, 2018 at 12:19:41 CET Greg Kroah-Hartman wrote:
> > On Wed, Jan 03, 2018 at 11:49:08AM +0100, Markus wrote:
> > > Hello!
> > >
> > > ORC unwinder is enabled in stable for wider testing but still at least one
> > > bug is open:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=197035
> >
> > Random web links on mailing lists don't help much, please put the
> > information here in the email.
>
> Its not a random web link. Its the official kernel.org bugtracker. But nobody
> seems to be looking at it.
Not all subsystems use bugzilla.kernel.org, sorry. Email is the
preferred way for almost all subsystems.
> > > objtool will segfault because a NULL pointer is dereferenced.
> >
> > And how are you reproducing this?
>
> Just building the kernel with ORC enabled.
> (At least for me. Using framepointers compiles, enabling ORC again breaks it.)
> gcc 6.4.0 (In bug report others were tested as well.)
> elfutils 0.170
> What else may be interesting?
Have you tried gcc 7?
What distro is this? Hopefully not hardened Gentoo? :)
> > > Is a NULL pointer sym valid?
> > > If a NULL pointer is invalid, it has to be checked why it is sometimes
> > > NULL.
> > What .config is triggering this problem?
> See attachment.
>
> > And does this show up on 4.14.11, and 4.15-rc6?
> Both: yes.
>
> /tools/objtool/objtool orc generate --no-fp "arch/x86/kernel/irq.o"
>
> => segfault.
Ugh, I can't duplicate here :(
Josh, any ideas?
greg k-h
next prev parent reply other threads:[~2018-01-03 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 10:49 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
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 [this message]
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=20180103141401.GC12918@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=M4rkusXXL@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome