diff options
| author | David Hildenbrand <[email protected]> | 2022-11-16 11:26:54 +0100 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-11-30 15:58:59 -0800 |
| commit | 70b96f24a441e5a7e0853e3893edd9dc58b67996 (patch) | |
| tree | 308ee57f85d90ed3d6c2173d5aa00bc171f120a5 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 7d96eb6a9164607df09c9589ed3ba9ef4e9cc2a6 (diff) | |
media: pci/ivtv: remove FOLL_FORCE usage
FOLL_FORCE is really only for ptrace access. R/O pinning a page is
supposed to fail if the VMA misses proper access permissions (no VM_READ).
Let's just remove FOLL_FORCE usage here; there would have to be a pretty
good reason to allow arbitrary drivers to R/O pin pages in a PROT_NONE
VMA. Most probably, FOLL_FORCE usage is just some legacy leftover.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: David Hildenbrand <[email protected]>
Acked-by: Hans Verkuil <[email protected]>
Cc: Andy Walls <[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