diff options
| author | David Hildenbrand <[email protected]> | 2022-11-16 11:26:51 +0100 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-11-30 15:58:59 -0800 |
| commit | 129e636fe9837fcfea68bfd368a07548d9880726 (patch) | |
| tree | f192f17e39dd6858b13e1dce0dd098de3cf7d30f /lib/test_fortify/write_overflow-memcpy.c | |
| parent | a9d0284033e974a355b806fdb5fbabf8301bcd16 (diff) | |
RDMA/siw: 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]
Signed-off-by: David Hildenbrand <[email protected]>
Reviewed-by: Jason Gunthorpe <[email protected]>
Cc: Bernard Metzler <[email protected]>
Cc: Leon Romanovsky <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions