Lines Matching refs:mlock_fixup

310 Both [do_]mlock() and [do_]mlockall() system call handlers call mlock_fixup()
312 this is the entire active address space of the task.  Note that mlock_fixup()
315 treated as a no-op, and mlock_fixup() simply returns.
318 below, mlock_fixup() will attempt to merge the VMA with its neighbors or split
320 VMA has been merged or split or neither, mlock_fixup() will call
357 mlock_fixup() filters several classes of "special" VMAs:
368    mlock_fixup() will call make_pages_present() in the hugetlbfs VMA range to
374    mlock_fixup() treats these VMAs the same as hugetlbfs VMAs.  It calls
377 Note that for all of these special VMAs, mlock_fixup() does not set the
379 munlock(), munmap() or task exit.  Neither does mlock_fixup() account these
389 handled by mlock_fixup().  Again, if called for an already munlocked VMA,
390 mlock_fixup() simply returns.  Because of the VMA filtering discussed above,
394 If the VMA is VM_LOCKED, mlock_fixup() again attempts to merge or split off the
506 munlock_vma_pages_all() clears the VM_LOCKED VMA flag and, like mlock_fixup()