From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel 4.9.77 error segfault in compile.
Date: Wed, 24 Jan 2018 16:06:33 +1100 [thread overview]
Message-ID: <CAC=wYCHVY1Yd7R4xpaeWgVcsNMgdrZdAxMDABPQNQ19BBD_=sQ@mail.gmail.com> (raw)
In-Reply-To: <19f22bc3-ce42-e4e1-f4ab-52625a19f34c@charter.net>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Tue, Jan 23, 2018 at 2:51 AM, Corbin Bird <corbinbird@charter.net> wrote:
> Anyone else getting this error? ( kernel 4.9.77 )
>
> > CC fs/ext4/mballoc.o
> > CC fs/ext4/block_validity.o
> > CC fs/ext4/move_extent.o
> > CC fs/ext4/mmp.o
> > CC fs/ext4/indirect.o
> > fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
> > find jump dest instruction at .text+0x56c
> > CC fs/ext4/extents_status.o
> > /bin/sh: line 1: 31735 Segmentation fault ./tools/objtool/objtool
> > check "fs/ext4/extents_status.o"
> > make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
> > Error 139
> > make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
> > make: *** [Makefile:995: fs] Error 2
>
>
FYI, this is from 4.14.15's ChangeLog, doesn't appear to be in 4.9.78
though.
commit f41b2d7ee791e845147a3e3cafb25493dca6870a
Author: Josh Poimboeuf <jpoimboe@redhat.com>
Date: Mon Jan 15 08:17:07 2018 -0600
objtool: Fix seg fault with gold linker
commit 2a0098d70640dda192a79966c14d449e7a34d675 upstream.
Objtool segfaults when the gold linker is used with
CONFIG_MODVERSIONS=y and CONFIG_UNWINDER_ORC=y.
With CONFIG_MODVERSIONS=y, the .o file gets passed to the linker before
being passed to objtool. The gold linker seems to strip unused ELF
symbols by default, which confuses objtool and causes the seg fault when
it's trying to generate ORC metadata.
Objtool should really be running immediately after GCC anyway, without a
linker call in between. Change the makefile ordering so that objtool is
called before the linker.
[-- Attachment #2: Type: text/html, Size: 2401 bytes --]
next prev parent reply other threads:[~2018-01-24 5:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:51 [gentoo-user] kernel 4.9.77 error segfault in compile Corbin Bird
2018-01-22 17:11 ` Alexander Kapshuk
2018-01-22 17:56 ` Rich Freeman
2018-01-23 2:34 ` Corbin Bird
2018-01-23 7:42 ` Alexander Kapshuk
2018-01-23 8:03 ` Corbin Bird
2018-01-23 8:19 ` Alexander Kapshuk
2018-01-23 17:28 ` Corbin Bird
2018-01-23 17:35 ` Rich Freeman
2018-01-23 17:59 ` Wol's lists
2018-01-23 19:14 ` Corbin Bird
2018-01-24 1:55 ` Corbin Bird
2018-01-24 2:17 ` Rich Freeman
2018-01-23 17:30 ` Rich Freeman
2018-01-24 5:06 ` Adam Carter [this message]
2018-01-24 19:56 ` Corbin Bird
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='CAC=wYCHVY1Yd7R4xpaeWgVcsNMgdrZdAxMDABPQNQ19BBD_=sQ@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.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