public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus <M4rkusXXL@web.de>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: objtool segfault with ORC unwinder enabled
Date: Wed, 03 Jan 2018 11:49:08 +0100	[thread overview]
Message-ID: <1537667.mbZVOcHbLR@markus> (raw)

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

objtool will segfault because a NULL pointer is dereferenced.

Is a NULL pointer sym valid?
If a NULL pointer is invalid, it has to be checked why it is sometimes NULL.

Thank you!
Markus

             reply	other threads:[~2018-01-03 10:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 10:49 Markus [this message]
2018-01-03 11:19 ` objtool segfault with ORC unwinder enabled 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
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=1537667.mbZVOcHbLR@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox