diff options
author | David Hildenbrand <[email protected]> | 2022-11-16 11:26:49 +0100 |
---|---|---|
committer | Andrew Morton <[email protected]> | 2022-11-30 15:58:58 -0800 |
commit | b40656aa7d559adc1fe689396dc58b92a9a27286 (patch) | |
tree | fb4a86378ab328b46e4c37093942378fa8631e31 /lib/mpi/mpiutil.c | |
parent | 84209e87c6963f928194a890399e24e8ad299db1 (diff) |
RDMA/umem: remove FOLL_FORCE usage
GUP now supports reliable R/O long-term pinning in COW mappings, such
that we break COW early. MAP_SHARED VMAs only use the shared zeropage so
far in one corner case (DAXFS file with holes), which can be ignored
because GUP does not support long-term pinning in fsdax (see
check_vma_flags()).
Consequently, FOLL_FORCE | FOLL_WRITE | FOLL_LONGTERM is no longer required
for reliable R/O long-term pinning: FOLL_LONGTERM is sufficient. So stop
using FOLL_FORCE, which is really only for ptrace access.
Link: https://lkml.kernel.org/r/[email protected]
Tested-by: Leon Romanovsky <[email protected]> [over mlx4 and mlx5]
Signed-off-by: David Hildenbrand <[email protected]>
Reviewed-by: Jason Gunthorpe <[email protected]>
Cc: Leon Romanovsky <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'lib/mpi/mpiutil.c')
0 files changed, 0 insertions, 0 deletions