diff options
| author | David Hildenbrand <[email protected]> | 2022-11-16 11:26:55 +0100 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-11-30 15:58:59 -0800 |
| commit | cb78a634f3f7ff743e19fbffcb72d794e4bd7f73 (patch) | |
| tree | d9a41e24f44dba92061142ae2ec929a753e902d2 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 70b96f24a441e5a7e0853e3893edd9dc58b67996 (diff) | |
mm/frame-vector: remove FOLL_FORCE usage
FOLL_FORCE is really only for ptrace access. According to commit
707947247e95 ("media: videobuf2-vmalloc: get_userptr: buffers are always
writable"), get_vaddr_frames() currently pins all pages writable as a
workaround for issues with read-only buffers.
FOLL_FORCE, however, seems to be a legacy leftover as it predates
commit 707947247e95 ("media: videobuf2-vmalloc: get_userptr: buffers are
always writable"). Let's just remove it.
Once the read-only buffer issue has been resolved, FOLL_WRITE could
again be set depending on the DMA direction.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: David Hildenbrand <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Acked-by: Hans Verkuil <[email protected]>
Acked-by: Tomasz Figa <[email protected]>
Cc: Marek Szyprowski <[email protected]>
Cc: Marek Szyprowski <[email protected]>
Cc: Mauro Carvalho Chehab <[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