Thread (57 messages) 57 messages, 11 authors, 2022-11-29

Re: [PATCH mm-unstable v1 20/20] mm: rename FOLL_FORCE to FOLL_PTRACE

From: Kees Cook <hidden>
Date: 2022-11-18 22:29:13
Also in: dri-devel, linux-alpha, linux-fsdevel, linux-kselftest, linux-media, linux-mips, linux-mm, linux-perf-users, linux-rdma, linux-samsung-soc, linux-security-module, lkml, sparclinux

On Fri, Nov 18, 2022 at 12:09:02PM +0100, Peter Zijlstra wrote:
On Wed, Nov 16, 2022 at 10:16:34AM -0800, Linus Torvalds wrote:
quoted
Following the history of it is a big of a mess, because there's a
number of renamings and re-organizations, but it seems to go back to
2007 and commit b6a2fea39318 ("mm: variable length argument support").
I went back and read parts of the discussions with Ollie, and the
.force=1 thing just magically appeared one day when we were sending
work-in-progress patches back and forth without mention of where it came
from :-/

And I certainly can't remember now..

Looking at it now, I have the same reaction as both you and Kees had, it
seems entirely superflous. So I'm all for trying to remove it.
Thanks for digging through the history! I've pushed the change to -next:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/execve&id=cd57e443831d8eeb083c7165bce195d886e216d4

-- 
Kees Cook
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help