Lines Matching refs:mlock_fixup

292 Both [do\_]mlock() and [do\_]mlockall() system call handlers call mlock_fixup()
294 this is the entire active address space of the task.  Note that mlock_fixup()
297 treated as a no-op, and mlock_fixup() simply returns.
300 below, mlock_fixup() will attempt to merge the VMA with its neighbors or split
302 VMA has been merged or split or neither, mlock_fixup() will call
339 mlock_fixup() filters several classes of "special" VMAs:
350    mlock_fixup() will call make_pages_present() in the hugetlbfs VMA range to
356    mlock_fixup() treats these VMAs the same as hugetlbfs VMAs.  It calls
359 Note that for all of these special VMAs, mlock_fixup() does not set the
361 munlock(), munmap() or task exit.  Neither does mlock_fixup() account these
372 handled by mlock_fixup().  Again, if called for an already munlocked VMA,
373 mlock_fixup() simply returns.  Because of the VMA filtering discussed above,
377 If the VMA is VM_LOCKED, mlock_fixup() again attempts to merge or split off the
516 munlock_vma_pages_all() clears the VM_LOCKED VMA flag and, like mlock_fixup()