)]}' { "commit": "272ddc8b37354c3fe111ab26d25e792629148eee", "tree": "78d4280320fbee5b4b37a839023b6a9ba34865ef", "parents": [ "07d9a380680d1c0eb51ef87ff2eab5c994949e69" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 24 19:00:44 2016 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 24 19:00:44 2016 -0700" }, "message": "proc: don\u0027t use FOLL_FORCE for reading cmdline and environment\n\nNow that Lorenzo cleaned things up and made the FOLL_FORCE users\nexplicit, it becomes obvious how some of them don\u0027t really need\nFOLL_FORCE at all.\n\nSo remove FOLL_FORCE from the proc code that reads the command line and\narguments from user space.\n\nThe mem_rw() function actually does want FOLL_FORCE, because gdd (and\npossibly many other debuggers) use it as a much more convenient version\nof PTRACE_PEEKDATA, but we should consider making the FOLL_FORCE part\nconditional on actually being a ptracer. This does not actually do\nthat, just moves adds a comment to that effect and moves the gup_flags\nsettings next to each other.\n\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "8e654468ab676900bdcfb029558a766e1b448691", "old_mode": 33188, "old_path": "fs/proc/base.c", "new_id": "adfc5b4986f53a658e04424e900c544430a69124", "new_mode": 33188, "new_path": "fs/proc/base.c" } ] }