linux-kernel - Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be reserved

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Aug 2019 12:09:56 +0100
From:   Mike Lothian <mike@...eburn.co.uk>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        "H.J. Lu" <hjl.tools@...il.com>,
        Tom Lendacky <thomas.lendacky@....com>, bhe@...hat.com,
        Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, lijiang@...hat.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be reserved

On Thu, 25 Jul 2019 at 07:59, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Wed, Jul 24, 2019 at 10:20:34PM +0200, Thomas Gleixner wrote:
> > On Wed, 24 Jul 2019, Thomas Gleixner wrote:
> >
> > > On Wed, 24 Jul 2019, Greg KH wrote:
> > > > On Wed, Jul 24, 2019 at 06:03:41PM +0200, Thomas Gleixner wrote:
> > > > > > Gotta love old tool-chains :(
> > > > >
> > > > > Oh yes. /me does archaeology to find a VM with old stuff
> > > >
> > > > I can provide a binary if you can't find anything.
> > >
> > > Found GNU ld (GNU Binutils for Debian) 2.25 and after fiddling with
> > > LD_PRELOAD it builds without failure.
> > >
> > > ld.gold from that binutils version dies with a segfault on various files ...
> >
> > Then tried that old ld.bfd with GCC8 and that causes ld.bfd to segfault on
> > every other file.
> >
> > Copied that config to the clang build directory and it causes the same
> > explosions with ld.bfd.
> >
> > What a time waste...
> >
> >
> >
>
> Ugh, sorry about this.  I can't seem to track it down either, and at
> this point am just going to punt and let the Android build people try to
> figure it out as it is their custom build system that is failing at the
> moment, only for x86, and if this single patch is reverted, it starts
> working again.
>
> voodo...
>
> thanks,
>
> greg k-h

As it's related. I've raised
https://bugzilla.kernel.org/show_bug.cgi?id=204495 about the
relocatition I'm seeing since switching back to ld.bfd - is this safe
to ignore? I'm guessing this is why gold isn't working as it can't do
them

Cheers

Mike