summaryrefslogtreecommitdiffstats
path: root/mm/gup.c
diff options
context:
space:
mode:
authorLinus Torvalds2016-10-25 04:00:44 +0200
committerLinus Torvalds2016-10-25 04:00:44 +0200
commit272ddc8b37354c3fe111ab26d25e792629148eee (patch)
tree78d4280320fbee5b4b37a839023b6a9ba34865ef /mm/gup.c
parentLinux 4.9-rc2 (diff)
downloadkernel-qcow2-linux-272ddc8b37354c3fe111ab26d25e792629148eee.tar.gz
kernel-qcow2-linux-272ddc8b37354c3fe111ab26d25e792629148eee.tar.xz
kernel-qcow2-linux-272ddc8b37354c3fe111ab26d25e792629148eee.zip
proc: don't use FOLL_FORCE for reading cmdline and environment
Now that Lorenzo cleaned things up and made the FOLL_FORCE users explicit, it becomes obvious how some of them don't really need FOLL_FORCE at all. So remove FOLL_FORCE from the proc code that reads the command line and arguments from user space. The mem_rw() function actually does want FOLL_FORCE, because gdd (and possibly many other debuggers) use it as a much more convenient version of PTRACE_PEEKDATA, but we should consider making the FOLL_FORCE part conditional on actually being a ptracer. This does not actually do that, just moves adds a comment to that effect and moves the gup_flags settings next to each other. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/gup.c')
0 files changed, 0 insertions, 0 deletions