On 11/03, Jann Horn wrote: > > This shouldn't change behavior in any way - at this point, there should be > no non-writable mappings, only the initial stack mapping -,
So this FOLL_FORCE just adds the unnecessary confusion, > but this change > makes it easier to reason about the correctness of the following commits > that place restrictions on forced memory writes. and to me it looks like a good cleanup regardless. Exactly because it is not clear why do we need FOLL_FORCE. > Signed-off-by: Jann Horn <j...@thejh.net> > Reviewed-by: Janis Danisevskis <jda...@android.com> Acked-by: Oleg Nesterov <o...@redhat.com>
