Re: [PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-08 Thread Dave Hansen
On 06/08/2016 02:23 AM, Michael Kerrisk (man-pages) wrote: > On 06/07/2016 10:47 PM, Dave Hansen wrote: >> > Are there any concerns with merging these into the x86 tree so >> > that they go upstream for 4.8? > I believe we still don't have up-to-date man pages, right? > Best from my POV to send

Re: [PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-08 Thread Dave Hansen
On 06/08/2016 02:23 AM, Michael Kerrisk (man-pages) wrote: > On 06/07/2016 10:47 PM, Dave Hansen wrote: >> > Are there any concerns with merging these into the x86 tree so >> > that they go upstream for 4.8? > I believe we still don't have up-to-date man pages, right? > Best from my POV to send

Re: [PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-08 Thread Michael Kerrisk (man-pages)
On 06/07/2016 10:47 PM, Dave Hansen wrote: > Are there any concerns with merging these into the x86 tree so > that they go upstream for 4.8? I believe we still don't have up-to-date man pages, right? Best from my POV to send them out in parallel with the implementation. Cheers, Michael --

Re: [PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-08 Thread Michael Kerrisk (man-pages)
On 06/07/2016 10:47 PM, Dave Hansen wrote: > Are there any concerns with merging these into the x86 tree so > that they go upstream for 4.8? I believe we still don't have up-to-date man pages, right? Best from my POV to send them out in parallel with the implementation. Cheers, Michael --

[PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-07 Thread Dave Hansen
Are there any concerns with merging these into the x86 tree so that they go upstream for 4.8? The updates here are pretty minor. Changes from v1: * updates to alloc/free patch description calling out that "in-use" pkeys may still be pkey_free()'d successfully. * Fixed a bug in the selftest

[PATCH 0/9] [v2] System Calls for Memory Protection Keys

2016-06-07 Thread Dave Hansen
Are there any concerns with merging these into the x86 tree so that they go upstream for 4.8? The updates here are pretty minor. Changes from v1: * updates to alloc/free patch description calling out that "in-use" pkeys may still be pkey_free()'d successfully. * Fixed a bug in the selftest