> Pingfan Liu <kernelfans@xxxxxxxxx> writes: > > > As for FOLL_LONGTERM, it is checked in the slow path > > __gup_longterm_unlocked(). But it is not checked in the fast path, > > which means a possible leak of CMA page to longterm pinned requirement > > through this crack. > > Shouldn't we disallow FOLL_LONGTERM with get_user_pages fastpath? W.r.t > dax check we need vma to ensure whether a long term pin is allowed or not. > If FOLL_LONGTERM is specified we should fallback to slow path. Yes, the fastpath bails to the slowpath if FOLL_LONGTERM _and_ DAX. But it does this while walking the page tables. I missed the CMA case and Pingfan's patch fixes this. We could check for CMA pages while walking the page tables but most agreed that it was not worth it. For DAX we already had checks for *_devmap() so it was easier to put the FOLL_LONGTERM checks there. Ira
