linux-kernel - [RFD] x86: The future of MPX

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: <alpine.DEB.2.21.1804272122390.1596@nanos.tec.linutronix.de>
Date:   Fri, 27 Apr 2018 21:37:30 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     LKML <linux-kernel@...r.kernel.org>
cc:     Dave Hansen <dave.hansen@...ux.intel.com>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Borislav Petkov <bp@...en8.de>
Subject: [RFD] x86: The future of MPX

Dave,

I've got the following MPX related information:

 .... But they [Intel] certainly haven't maintained the whole MPX support
 in GCC at all since two or three years (e.g. bootstrap with MPX was broken
 since forever), so now it's gone from GCC. ....

and I know that GCC is discussing MPX removal since May last year at least.
To the best of my knowledge clang does not support it either.

So what's the state of this stuff? If we don't have a compiler supporting
it how on earth is that useful or even testable for anyone who does not
have access to some magic Intel internal compiler version?

If that's the sad state of affairs, then we just should move the whole
stuff into staging or simply queue it for removal in 4.18.

Thanks,

	tglx