Lines Matching refs:guard

576 * For systems that implement stack protection using a guard memory region,
577   it's possible to overshoot the guard and corrupt adjacent data structures
585 CPU features for this purpose, or special read-only guard regions immediately
615 on write. Reserved memory will be used for the guard region.
622 MMU-based systems should not reserve RAM for the guard region and instead
641   the guard is unnecessary and shouldn't be unconditionally reserved.
645 * The required guard size is variable and depends on context. For example, some
648   completely overshooting a minimally-sized guard and corrupting adjacent
649   memory. Rather than unconditionally reserving a larger guard, the extra
660   system calls. If stack guards are implemented, a stack guard region must
700 The guard region, and any carve-out (if needed) would be configured as a
704   extra stack memory. An overflow will eventually crash into the guard region.
710   handling a system call will crash into the guard region.
714 memory, each with non-present virtual guard pages below them to catch runtime
717 Other platform data may be stored before the guard region, but this is highly
759    | MPU guard carve-out         |
765 The guard carve-out in the thread stack object is only used if the thread is
766 running in supervisor mode. If the thread drops to user mode, there is no guard