linux-kernel - Re: [PATCH 3.19 3/3] x86, mpx: Change the MPX enable/disable API to arch

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: <54AC1FFB.7030504@linux.intel.com>
Date:	Tue, 06 Jan 2015 09:48:43 -0800
From:	Dave Hansen <dave.hansen@...ux.intel.com>
To:	Andy Lutomirski <luto@...capital.net>,
	Andi Kleen <andi@...stfloor.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	X86 ML <x86@...nel.org>, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3.19 3/3] x86, mpx: Change the MPX enable/disable API
 to arch_prctl

On 01/05/2015 09:59 PM, Andy Lutomirski wrote:
> But I decided to check whether libmpx links against glibc, and I can't
> find sources for it at all.  Do they exist?  Is there any code with
> source available that invokes this prctl?
> 
> If not, I personally have very little sympathy for the argument that a
> binary buried in the depths of the Intel SDE would need to change if
> we switched to using arch_prctl.  And I think that it should issue the
> syscall itself without using glibc, in which case the syscall wrapper
> issue is moot.

Andy, as I mentioned previously, there is code in a GCC branch that uses
the existing prctl().  It's also been posted for review to one of the
GCC mailing lists.  I've been told that it will be in gcc 5.0.

The Intel SDE does not use the prctl() in any way that I know of.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/