linux-kernel - Re: undefined reference to `_GLOBAL_OFFSET_TABLE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170822221443.006a2121@roar.ozlabs.ibm.com>
Date:   Tue, 22 Aug 2017 22:14:43 +1000
From:   Nicholas Piggin <npiggin@...il.com>
To:     Michal Simek <monstr@...str.eu>
Cc:     kbuild test robot <fengguang.wu@...el.com>, kbuild-all@...org,
        linux-kernel@...r.kernel.org,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: undefined reference to `_GLOBAL_OFFSET_TABLE_'

On Tue, 22 Aug 2017 11:19:02 +0200
Michal Simek <monstr@...str.eu> wrote:

> On 20.8.2017 05:36, Nicholas Piggin wrote:
> > On Sun, 20 Aug 2017 08:37:36 +0800
> > kbuild test robot <fengguang.wu@...el.com> wrote:
> >   
> >> Hi Nicholas,
> >>
> >> FYI, the error/warning still remains.  
> > 
> > Still same answer as before, i.e., it seems to be this toolchain bug:
> > 
> > https://sourceware.org/bugzilla/show_bug.cgi?id=21017
> > 
> > I've had no response from the microblaze maintainer, so please stop
> > generating this warning now. If we get a bug report from a user who
> > actually cares and will test toolchain fixes then we can easily work
> > with them.
> > 
> > Many thanks for the very good service this build system provides!  
> 
> Can you please point me to the log?

Hmm, don't know if they keep a full log, but the error is

   mm/slub.o: In function `__slab_free.isra.13':
>> (.text+0x1038): undefined reference to `_GLOBAL_OFFSET_TABLE_'  
   scripts/link-vmlinux.sh: line 93: 48917 Segmentation fault      ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${objects}

I suspect the change to thin archives, allowed the linker more
flexibility to satisfy all relocations with GOT relative. And
that would cause the bug.

If you could verify that the upstream kernel build succeeds with
an upstream binutils using allnoconfig, then we could see about
updating the kbuild test robot's toolchain.

Thanks,
Nick