Lines Matching refs:guard

585 * For systems that implement stack protection using a guard memory region,
586   it's possible to overshoot the guard and corrupt adjacent data structures
594 CPU features for this purpose, or special read-only guard regions immediately
624 on write. Reserved memory will be used for the guard region.
631 MMU-based systems should not reserve RAM for the guard region and instead
650   the guard is unnecessary and shouldn't be unconditionally reserved.
654 * The required guard size is variable and depends on context. For example, some
657   completely overshooting a minimally-sized guard and corrupting adjacent
658   memory. Rather than unconditionally reserving a larger guard, the extra
669   system calls. If stack guards are implemented, a stack guard region must
709 The guard region, and any carve-out (if needed) would be configured as a
713   extra stack memory. An overflow will eventually crash into the guard region.
719   handling a system call will crash into the guard region.
723 memory, each with non-present virtual guard pages below them to catch runtime
726 Other platform data may be stored before the guard region, but this is highly
768    | MPU guard carve-out         |
774 The guard carve-out in the thread stack object is only used if the thread is
775 running in supervisor mode. If the thread drops to user mode, there is no guard