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
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
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
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
4 matches
Mail list logo