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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.21.1907241751240.1791@nanos.tec.linutronix.de>
Date:   Wed, 24 Jul 2019 18:01:03 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Greg KH <gregkh@...uxfoundation.org>
cc:     "H.J. Lu" <hjl.tools@...il.com>,
        Mike Lothian <mike@...eburn.co.uk>,
        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 Wed, 24 Jul 2019, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > > Sorry, I saw that after writing that.  You are right, if the others
> > > don't object, that's fine with me.  I'll go poke the various build
> > > systems that are failing right now on 5.3-rc1 and try to get them fixed
> > > for this reason.
> > 
> > Ok, I dug around and the gold linker is not being used here, only clang
> > to build the source and GNU ld to link, and I am still seeing this
> > error.
> 
> Odd combo.

Ha. Not really. I did not switch ld with LD=... so it's using the default GNU ld.

> > Hm, clang 8 does not cause this error, but clang 9 does.  Let me go poke
> > the people who are providing this version of clang to see if there's
> > something they can figure out.
> 
> Let me try that with my clang variant. Which version of GNU ld are you
> using?

Works with a very recent build of the clang-9 branch and ld version 2.31.1

Thanks,

	tglx