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]
Message-ID: <20180209230041.GI10945@tassilo.jf.intel.com>
Date:   Fri, 9 Feb 2018 15:00:41 -0800
From:   Andi Kleen <ak@...ux.intel.com>
To:     Chris Wilson <chris@...is-wilson.co.uk>
Cc:     Arnd Bergmann <arnd@...db.de>, x86@...nel.org,
        Nicolas Pitre <nico@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] x86 bugfixes for LTO

On Fri, Feb 09, 2018 at 10:24:33PM +0000, Chris Wilson wrote:
> Quoting Arnd Bergmann (2018-02-02 14:54:28)
> > Here are three bugfixes for x86 that I needed to get LTO-enabled
> > kernels to build reliably. I'm not sure abouto that first one
> > though.
> 
> Is there a howto on how to build LTO kernels? I tried Andi's lto-415-2
> branch, but linking fails with lots of arcane PIE-vs-PIC errors. We are
> wanting to investigate how we can use LTO to reduce our (i915.ko) module
> size (by e.g. supporting a subset of chipsets).

What are the errors? Kernel shouldn't use PIE or PIC

-Andi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ