diff options
| author | David Hildenbrand <[email protected]> | 2022-11-16 11:26:53 +0100 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-11-30 15:58:59 -0800 |
| commit | 7d96eb6a9164607df09c9589ed3ba9ef4e9cc2a6 (patch) | |
| tree | 1ec0ccb47f1cf09d947ab81bc342c0b9e2068d01 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 3298de2c66e0276abe6b95041fd3605a377523fc (diff) | |
drm/etnaviv: 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()).
commit cd5297b0855f ("drm/etnaviv: Use FOLL_FORCE for userptr")
documents that FOLL_FORCE | FOLL_WRITE was really only used for reliable
R/O pinning.
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: Daniel Vetter <[email protected]>
Cc: Lucas Stach <[email protected]>
Cc: Russell King <[email protected]>
Cc: Christian Gmeiner <[email protected]>
Cc: David Airlie <[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