mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Enabling the ORC unwinder generates invalid .o files.
Date: Wed, 18 Jul 2018 14:25:08 +0000	[thread overview]
Message-ID: <ec49fdfc7c0b421b8818301cc44de659@AcuMS.aculab.com> (raw)

As was discovered last september (https://lkml.org/lkml/2017/9/14/561)
running objtool to generate the orc unwind data will generate invalid
object files on an systems where libelf.so hasn't been patched.

I've just spent a day debugging the same issue - as far as the
corrupted section headers - before managing to get a search tell
me something other than I was running an old distribution.

Since then the orc unwinder has been made the default on x86-64.
So anyone running anything other than the very latest distributions
can't actually build a kernel from sources.
The 'allmodconfig' build goes particularly badly.

It wouldn't be quite as annoying if the build detected the failure
and suggested updating libelf (I found 0.165 to replace 0.153) or
disabling orc.

The kernel build claims to support much older compilers than the
gcc 4.7.3 I'm trying to use, so I'd expect it to compile with
the version of libelf of the same vintage.

Perhaps the solution is to put a copy of (the required parts of)
the libelf sources with the objtool sources so that a known
version is used.
This would also safe the problems that also arise because libelf
isn't installed by default.

	David
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

Please consider the environment and don't print this e-mail unless you really need to


                 reply	other threads:[~2018-07-18 14:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ec49fdfc7c0b421b8818301cc44de659@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kernel@vger.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