Re: [PATCH v3 1/3] fs/exec: don't force writing memory access

2016-11-03 Thread Oleg Nesterov
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

Re: [PATCH v3 1/3] fs/exec: don't force writing memory access

2016-11-03 Thread Oleg Nesterov
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

[PATCH v3 1/3] fs/exec: don't force writing memory access

2016-11-02 Thread Jann Horn
This shouldn't change behavior in any way - at this point, there should be no non-writable mappings, only the initial stack mapping -, but this change makes it easier to reason about the correctness of the following commits that place restrictions on forced memory writes. Signed-off-by: Jann Horn

[PATCH v3 1/3] fs/exec: don't force writing memory access

2016-11-02 Thread Jann Horn
This shouldn't change behavior in any way - at this point, there should be no non-writable mappings, only the initial stack mapping -, but this change makes it easier to reason about the correctness of the following commits that place restrictions on forced memory writes. Signed-off-by: Jann Horn