Re: [PATCH v2 2/4] mm: fail get_vaddr_frames() for filesystem-dax mappings

2017-11-27 Thread Dan Williams
On Mon, Nov 27, 2017 at 8:15 AM, Jan Kara wrote: > On Tue 14-11-17 11:56:39, Dan Williams wrote: >> Until there is a solution to the dma-to-dax vs truncate problem it is >> not safe to allow V4L2, Exynos, and other frame vector users to create >> long standing / irrevocable memory registrations ag

Re: [PATCH v2 2/4] mm: fail get_vaddr_frames() for filesystem-dax mappings

2017-11-27 Thread Jan Kara
On Tue 14-11-17 11:56:39, Dan Williams wrote: > Until there is a solution to the dma-to-dax vs truncate problem it is > not safe to allow V4L2, Exynos, and other frame vector users to create > long standing / irrevocable memory registrations against filesytem-dax > vmas. > > Cc: Inki Dae > Cc: Se

[PATCH v2 2/4] mm: fail get_vaddr_frames() for filesystem-dax mappings

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 V4L2, Exynos, and other frame vector users to create long standing / irrevocable memory registrations against filesytem-dax vmas. Cc: Inki Dae Cc: Seung-Woo Kim Cc: Joonyoung Shim Cc: Kyungmin Park Cc: Maur