Home
last modified time | relevance | path

Searched refs:mlock_fixup (Results 1 – 2 of 2) sorted by relevance

/kernel/linux/linux-5.10/Documentation/vm/
Dunevictable-lru.rst292 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
[all …]
/kernel/linux/linux-5.10/mm/
Dmlock.c524 static int mlock_fixup(struct vm_area_struct *vma, struct vm_area_struct **prev, in mlock_fixup() function
619 error = mlock_fixup(vma, &prev, nstart, tmp, newflags); in apply_vma_lock_flags()
797 mlock_fixup(vma, &prev, vma->vm_start, vma->vm_end, newflags); in apply_mlockall_flags()