mm: handle shared faults under the VMA lock
authorMatthew Wilcox (Oracle) <willy@infradead.org>
Fri, 6 Oct 2023 19:53:15 +0000 (20:53 +0100)
committerAndrew Morton <akpm@linux-foundation.org>
Wed, 18 Oct 2023 21:34:14 +0000 (14:34 -0700)
commit4ed4379881aa62588aba6442a9f362a8cf7624e6
treea373d55dedf8fe2cdf03abc18ad29dd381d084d0
parent164b06f238b986317131e6b61b2f22aabcbc2cc0
mm: handle shared faults under the VMA lock

There are many implementations of ->fault and some of them depend on
mmap_lock being held.  All vm_ops that implement ->map_pages() end up
calling filemap_fault(), which I have audited to be sure it does not rely
on mmap_lock.  So (for now) key off ->map_pages existing as a flag to
indicate that it's safe to call ->fault while only holding the vma lock.

Link: https://lkml.kernel.org/r/20231006195318.4087158-4-willy@infradead.org
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/memory.c