Re: [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

2016-07-07 Thread Dave Hansen
On 07/07/2016 07:40 AM, Mel Gorman wrote: > On Thu, Jul 07, 2016 at 05:47:20AM -0700, Dave Hansen wrote: >> From: Dave Hansen >> PF_PK means that a memory access violated the protection key >> access restrictions. It is unconditionally an access_error() >> because the permissions set on the VMA d

Re: [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

2016-07-07 Thread Mel Gorman
On Thu, Jul 07, 2016 at 05:47:20AM -0700, Dave Hansen wrote: > > From: Dave Hansen > > PF_PK means that a memory access violated the protection key > access restrictions. It is unconditionally an access_error() > because the permissions set on the VMA don't matter (the PKRU > value overrides it

[PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

2016-07-07 Thread Dave Hansen
From: Dave Hansen PF_PK means that a memory access violated the protection key access restrictions. It is unconditionally an access_error() because the permissions set on the VMA don't matter (the PKRU value overrides it), and we never "resolve" PK faults (like how a COW can "resolve write faul

[PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

2016-06-08 Thread Dave Hansen
From: Dave Hansen PF_PK means that a memory access violated the protection key access restrictions. It is unconditionally an access_error() because the permissions set on the VMA don't matter (the PKRU value overrides it), and we never "resolve" PK faults (like how a COW can "resolve write faul

[PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

2016-06-07 Thread Dave Hansen
From: Dave Hansen PF_PK means that a memory access violated the protection key access restrictions. It is unconditionally an access_error() because the permissions set on the VMA don't matter (the PKRU value overrides it), and we never "resolve" PK faults (like how a COW can "resolve write faul