David Hildenbrand cb78a634f3 mm/frame-vector: remove FOLL_FORCE usage ... FOLL_FORCE is really only for ptrace access. According to commit 707947247e ("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 707947247e ("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/20221116102659.70287-17-david@redhat.com Signed-off-by: David Hildenbrand <david@redhat.com> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Acked-by: Hans Verkuil <hverkuil-cisco@xs4all.nl> Acked-by: Tomasz Figa <tfiga@chromium.org> Cc: Marek Szyprowski <m.szyprowski@samsung.com> Cc: Marek Szyprowski <m.szyprowski@samsung.com> Cc: Mauro Carvalho Chehab <mchehab@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>		2022-11-30 15:58:59 -08:00
..
frame_vector.c	mm/frame-vector: remove FOLL_FORCE usage	2022-11-30 15:58:59 -08:00
Kconfig	media: videobuf2: Move frame_vector into media subsystem	2021-01-12 14:15:31 +01:00
Makefile	media: Makefiles: sort entries where it fits	2022-03-14 09:42:59 +01:00
vb2-trace.c
videobuf2-core.c	media: vb2: videobuf -> videobuf2	2022-08-29 15:38:09 +02:00
videobuf2-dma-contig.c	drm for 5.18-rc1	2022-03-24 16:19:43 -07:00
videobuf2-dma-sg.c	media: videobuf2-dma-sg.c: kvmalloc_array -> kvcalloc	2022-05-13 11:02:22 +02:00
videobuf2-dvb.c	media: vb2: videobuf -> videobuf2	2022-08-29 15:38:09 +02:00
videobuf2-memops.c	mm/frame-vector: Use FOLL_LONGTERM	2021-01-12 14:15:17 +01:00
videobuf2-v4l2.c	media: videobuf2: Remove vb2_find_timestamp()	2022-08-30 14:44:45 +02:00
videobuf2-vmalloc.c	dma-buf-map: Rename to iosys-map	2022-02-07 16:35:35 -08:00