From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751054AbcGNIHS (ORCPT ); Thu, 14 Jul 2016 04:07:18 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34669 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750865AbcGNIHG (ORCPT ); Thu, 14 Jul 2016 04:07:06 -0400 Date: Thu, 14 Jul 2016 10:07:01 +0200 From: Ingo Molnar To: Andy Lutomirski Cc: Dave Hansen , Thomas Gleixner , Dave Hansen , Al Viro , X86 ML , Hugh Dickins , Andrew Morton , Linux API , Mel Gorman , Linus Torvalds , linux-arch , "linux-mm@kvack.org" , Arnd Bergmann , Peter Zijlstra , "linux-kernel@vger.kernel.org" , "H. Peter Anvin" Subject: Re: [PATCH 6/9] x86, pkeys: add pkey set/get syscalls Message-ID: <20160714080701.GA14613@gmail.com> References: <20160708071810.GA27457@gmail.com> <577FD587.6050101@sr71.net> <20160709083715.GA29939@gmail.com> <5783AE8F.3@sr71.net> <5783BFB0.70203@intel.com> <20160713075550.GA515@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andy Lutomirski wrote: > On Wed, Jul 13, 2016 at 12:56 AM, Ingo Molnar wrote: > > > > * Andy Lutomirski wrote: > > > >> > If we push a PKRU value into a thread between the rdpkru() and wrpkru(), we'll > >> > lose the content of that "push". I'm not sure there's any way to guarantee > >> > this with a user-controlled register. > >> > >> We could try to insist that user code uses some vsyscall helper that tracks > >> which bits are as-yet-unassigned. That's quite messy, though. > > > > Actually, if we turned the vDSO into something more like a minimal user-space > > library with the ability to run at process startup as well to prepare stuff > > then it's painful to get right only *once*, and there will be tons of other > > areas where a proper per thread data storage on the user-space side would be > > immensely useful! > > Doing this could be tricky: how exactly is the vDSO supposed to find per-thread > data without breaking existing glibc? So I think the way this could be done is by allocating it itself. The vDSO vma itself is 'external' to glibc as well to begin with - this would be a small extension to that concept. Thanks, Ingo