linux-kernel - Is LTO_REFERENCE_INITCALL() still needed?

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

Message-ID: <CAB=NE6W6Eh1tU=NXf20f-CPYeT22mtXGzrYqM9W-f14dGBrEsA@mail.gmail.com>
Date:	Thu, 23 Jun 2016 16:34:54 -0700
From:	"Luis R. Rodriguez" <mcgrof@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	X86 ML <x86@...nel.org>, Borislav Petkov <bp@...en8.de>,
	Andy Lutomirski <luto@...capital.net>
Subject: Is LTO_REFERENCE_INITCALL() still needed?

Andi,

is LTO_REFERENCE_INITCAL() still needed?

I see external stuff like this:

https://github.com/neo-technologies/linux-next/blob/master/scripts/Makefile.lto

But nothing quite obviously setting these upstream. I'm probably just
missing something obvious though. Either way I figured now would be a
good time to ask as I have other code that would use this, the linker
table stuff I've been working. If we can avoid propagating more use of
LTO_REFERENCE_INITCALL() then great. If we still need it its probably
good to document this a bit more as can't see anything super clear.

  Luis