On 01/23/2018 11:06 PM, Adam Carter wrote:
>
> FYI, this is from 4.14.15's ChangeLog, doesn't appear to be in 4.9.78
> though.
>
> commit f41b2d7ee791e845147a3e3cafb25493dca6870a
> Author: Josh Poimboeuf <jpoim...@redhat.com <mailto:jpoim...@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.
.
FYI :
Found the culprit ... ( very late last night )
.
sys-kernel/gentoo-sources has a USE Flag of 'experimental'
The experimental patch enables additional choices for CPU.
The last kernel version with no problem was 4.9.76-r1
The choice that worked before was : AMD Piledriver
That induces the error now.
.
When I compiled with CPU set to :
K-8 --> no problem
Generic x86_64 --> no problem
.
That was the only change made in 'menuconfig' before every test compile.
.
Now I know why all the warnings from the 'objtool', during compile, also
disappeared.
( With CPU set to either : K-8, Generic x86_64 )
> 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.
Thinking the 'experimental patch' may be needing some attention.
.
So ... now I am looking at filling a bug report ( if appropriate ) on
Gentoo's bug tracker.
.
Thanks to every one who chipped in with suggestions.
.
Corbin
