Re: [PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

2017-12-14 Thread Peter Zijlstra
On Thu, Dec 14, 2017 at 08:35:50AM -0800, Andy Lutomirski wrote: > > @@ -3252,6 +3256,7 @@ static const struct vm_operations_struct > > .fault = special_mapping_fault, > > .mremap = special_mapping_mremap, > > .name = special_mapping_name, > > + .split = special_mappi

Re: [PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

2017-12-14 Thread Andy Lutomirski
On Thu, Dec 14, 2017 at 4:08 AM, Peter Zijlstra wrote: > On Thu, Dec 14, 2017 at 01:03:37PM +0100, Thomas Gleixner wrote: >> On Thu, 14 Dec 2017, Peter Zijlstra wrote: >> > So here's a second posting of the VMA based LDT implementation; now without >> > most of the crazy. >> > >> > I took out the

Re: [PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

2017-12-14 Thread Peter Zijlstra
On Thu, Dec 14, 2017 at 01:03:37PM +0100, Thomas Gleixner wrote: > On Thu, 14 Dec 2017, Peter Zijlstra wrote: > > So here's a second posting of the VMA based LDT implementation; now without > > most of the crazy. > > > > I took out the write fault handler and the magic LAR touching code. > > > >

Re: [PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

2017-12-14 Thread Thomas Gleixner
On Thu, 14 Dec 2017, Peter Zijlstra wrote: > So here's a second posting of the VMA based LDT implementation; now without > most of the crazy. > > I took out the write fault handler and the magic LAR touching code. > > Additionally there are a bunch of patches that address generic vm issue. > >

[PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

2017-12-14 Thread Peter Zijlstra
So here's a second posting of the VMA based LDT implementation; now without most of the crazy. I took out the write fault handler and the magic LAR touching code. Additionally there are a bunch of patches that address generic vm issue. - gup() access control; In specific I looked at accessing !