diff options
| author |   Matthew Wilcox (Oracle) <willy@infradead.org> | 2023-10-06 20:53:15 +0100 |
|---|---|---|
| committer |   Andrew Morton <akpm@linux-foundation.org> | 2023-10-18 14:34:14 -0700 |
| commit | 4ed4379881aa62588aba6442a9f362a8cf7624e6 (patch) | |
| tree | a373d55dedf8fe2cdf03abc18ad29dd381d084d0 /mm/rmap.c | |
| parent | mm: call wp_page_copy() under the VMA lock (diff) | |
| download | wireguard-linux-4ed4379881aa62588aba6442a9f362a8cf7624e6.tar.xz wireguard-linux-4ed4379881aa62588aba6442a9f362a8cf7624e6.zip | |
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>
Diffstat (limited to 'mm/rmap.c')
0 files changed, 0 insertions, 0 deletions