Re: [PATCH v2 1/4] mm: introduce get_user_pages_longterm

2017-11-21 Thread Dan Williams
On Tue, Nov 21, 2017 at 3:05 PM, Andrew Morton wrote: > > On Tue, 14 Nov 2017 11:56:34 -0800 Dan Williams > wrote: > > > Until there is a solution to the dma-to-dax vs truncate problem it is > > not safe to allow long standing memory registrations against > > filesytem-dax vmas. Device-dax vmas

Re: [PATCH v2 1/4] mm: introduce get_user_pages_longterm

2017-11-21 Thread Andrew Morton
On Tue, 14 Nov 2017 11:56:34 -0800 Dan Williams wrote: > Until there is a solution to the dma-to-dax vs truncate problem it is > not safe to allow long standing memory registrations against > filesytem-dax vmas. Device-dax vmas do not have this problem and are > explicitly allowed. > > This is

Re: [PATCH v2 1/4] mm: introduce get_user_pages_longterm

2017-11-21 Thread Andrew Morton
On Tue, 14 Nov 2017 11:56:34 -0800 Dan Williams wrote: > Until there is a solution to the dma-to-dax vs truncate problem it is > not safe to allow long standing memory registrations against > filesytem-dax vmas. Device-dax vmas do not have this problem and are > explicitly allowed. > > This is

[PATCH v2 1/4] mm: introduce get_user_pages_longterm

2017-11-14 Thread Dan Williams
Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow long standing memory registrations against filesytem-dax vmas. Device-dax vmas do not have this problem and are explicitly allowed. This is temporary until a "memory registration with layout-lease" mechanism ca