From: Daniel Borkmann <[email protected]>
Date: Tue, 1 Jan 2019 21:49:21 +0100
> Restrict stack pointer arithmetic for unpriviledged users in that
> arithmetic itself must not go out of bounds as opposed to the actual
> access later on. Therefore after each adjust_ptr_min_max_vals() with
> a stack pointer as a destination we simulate a check_stack_access()
> of 1 byte on the destination and once that fails the program is
> rejected for unpriviledged program loads. This is analoge to map
^^^^^^^
Should be "analog".
