Searched refs:mlock_fixup (Results 1 – 2 of 2) sorted by relevance
/linux-6.6.21/mm/ |
D | mlock.c | 412 static int mlock_fixup(struct vma_iterator *vmi, struct vm_area_struct *vma, in mlock_fixup() function 514 error = mlock_fixup(&vmi, vma, &prev, nstart, tmp, newflags); in apply_vma_lock_flags() 697 mlock_fixup(&vmi, vma, &prev, vma->vm_start, vma->vm_end, in apply_mlockall_flags()
|
/linux-6.6.21/Documentation/mm/ |
D | unevictable-lru.rst | 291 mlock(), mlock2() and mlockall() system call handlers proceed to mlock_fixup() 293 this is the entire active address space of the task. Note that mlock_fixup() 296 treated as a no-op and mlock_fixup() simply returns. 299 below, mlock_fixup() will attempt to merge the VMA with its neighbors or split 340 mlock_fixup() filters several classes of "special" VMAs: 360 Note that for all of these special VMAs, mlock_fixup() does not set the 362 munlock(), munmap() or task exit. Neither does mlock_fixup() account these 370 mlock_fixup() function as mlock(), mlock2() and mlockall() system calls are. 371 If called to munlock an already munlocked VMA, mlock_fixup() simply returns. 375 If the VMA is VM_LOCKED, mlock_fixup() again attempts to merge or split off the
|