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:   Tue, 23 Jul 2019 15:31:32 +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 Tue, 23 Jul 2019, Greg KH wrote:
> On Mon, Jul 15, 2019 at 01:16:48PM -0700, H.J. Lu wrote:
> > >
> > 
> > Since building a workable kernel for different kernel configurations isn't a
> > requirement for gold, I don't recommend gold for kernel.
> 
> Um, it worked before this commit, and now it doesn't.  "Some" companies
> are using gold for linking the kernel today...

gold is known to fail the kernel build. x32 vdso linking is not working
since years and just because it 'works' for some configurations and breaks
for no valid reasons even with those configurations is just not good
enough.

As there is obviously no priority for fixing gold to work proper with the
kernel, I'm not at all interested in these 'regression' reports and in odd
'fixes' which just end up reverting or modifying perfectly valid changes
without understanding the root cause, i.e. the most horrible engineering
principle: duct-taping.

TBH, I'm tired of it. We fail the build for clang if it does not support
asm gotos and the clang people are actively working on fixing it and we're
helping them as much as we can. The companies who used clang nevertheless
have been on their own for years and if someone wants to use gold then
nobody is preventing them from doing so. They can keep their duct-tape in
their own trees.

See this thread for further discussion:

 https://lkml.kernel.org/r/alpine.DEB.2.21.1907161434260.1767@nanos.tec.linutronix.de

Thanks,

	tglx