From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754332AbbAFEEd (ORCPT ); Mon, 5 Jan 2015 23:04:33 -0500 Received: from one.firstfloor.org ([193.170.194.197]:55432 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752933AbbAFEEa (ORCPT ); Mon, 5 Jan 2015 23:04:30 -0500 Date: Tue, 6 Jan 2015 05:04:28 +0100 From: Andi Kleen To: Andy Lutomirski Cc: Dave Hansen , Andi Kleen , "linux-kernel@vger.kernel.org" , X86 ML , Thomas Gleixner Subject: Re: [PATCH 3.19 3/3] x86, mpx: Change the MPX enable/disable API to arch_prctl Message-ID: <20150106040428.GR2915@two.firstfloor.org> References: <54A64E6D.1020304@linux.intel.com> <87mw5x0xjz.fsf@tassilo.jf.intel.com> <54AAFFA3.6000901@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > We should avoid arch_prctl because glibc won't add a syscall stub that > libgcc or whatever would want? My mind boggles. Please turn brain on before posting. Of course they would add it. But only in the next version. Which means everyone using older glibc would be out of luck. So all the users would be stuck using syscall(). Anything you may gain in the kernel would be totally made up by that. BTW I added arch_prctl, but in hindsight it wasn't good idea. -Andi