Linus Torvalds e6bbad7571 mm: always expand the stack with the mmap write lock held ... commit 8d7071af89 upstream This finishes the job of always holding the mmap write lock when extending the user stack vma, and removes the 'write_locked' argument from the vm helper functions again. For some cases, we just avoid expanding the stack at all: drivers and page pinning really shouldn't be extending any stacks. Let's see if any strange users really wanted that. It's worth noting that architectures that weren't converted to the new lock_mm_and_find_vma() helper function are left using the legacy "expand_stack()" function, but it has been changed to drop the mmap_lock and take it for writing while expanding the vma. This makes it fairly straightforward to convert the remaining architectures. As a result of dropping and re-taking the lock, the calling conventions for this function have also changed, since the old vma may no longer be valid. So it will now return the new vma if successful, and NULL - and the lock dropped - if the area could not be extended. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> [6.1: Patch drivers/iommu/io-pgfault.c instead] Signed-off-by: Samuel Mendoza-Jonas <samjonas@amazon.com> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-07-01 13:16:25 +02:00
..
Makefile	…
cache.c	…
fault.c	mm: always expand the stack with the mmap write lock held	2023-07-01 13:16:25 +02:00
init.c	openrisc/mm: enable ARCH_HAS_VM_GET_PAGE_PROT	2022-07-17 17:14:38 -07:00
ioremap.c	openrisc: io: Define iounmap argument as volatile	2022-07-30 05:50:15 +09:00
tlb.c	…