mm: Always downgrade mmap_lock if requested
authorMatthew Wilcox (Oracle) <willy@infradead.org>
Thu, 29 Jun 2023 19:14:14 +0000 (20:14 +0100)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sat, 1 Jul 2023 15:10:56 +0000 (08:10 -0700)
Now that stack growth must always hold the mmap_lock for write, we can
always downgrade the mmap_lock to read and safely unmap pages from the
page table, even if we're next to a stack.

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/mmap.c

index 3e5793e..141c618 100644 (file)
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2551,19 +2551,8 @@ do_vmi_align_munmap(struct vma_iterator *vmi, struct vm_area_struct *vma,
        /* Point of no return */
        mm->locked_vm -= locked_vm;
        mm->map_count -= count;
-       /*
-        * Do not downgrade mmap_lock if we are next to VM_GROWSDOWN or
-        * VM_GROWSUP VMA. Such VMAs can change their size under
-        * down_read(mmap_lock) and collide with the VMA we are about to unmap.
-        */
-       if (downgrade) {
-               if (next && (next->vm_flags & VM_GROWSDOWN))
-                       downgrade = false;
-               else if (prev && (prev->vm_flags & VM_GROWSUP))
-                       downgrade = false;
-               else
-                       mmap_write_downgrade(mm);
-       }
+       if (downgrade)
+               mmap_write_downgrade(mm);
 
        /*
         * We can free page tables without write-locking mmap_lock because VMAs