Lines Matching refs:that

7 The Read-Only Allocator is an extension of the zone allocator that facilitates
21 as PAC, means that today's attacker favors data-only attacks to achieve
23 target data structures in the kernel's memory that effectively disables or
26 By necessity, we store lots of data on the heap that informs the various
34 mechanism, but unfortunately that doesn't cater for dynamic runtime
37 This is where the Read-Only Allocator provides its defense: we observe that
38 the majority of security-sensitive data that we allocate on the heap tends to
45 relatively expensive `zalloc_ro_mut` function.  By insisting that data be
47 of targeting that data towards the cost of seizing control of kernel
60    "back reference") that is validated when traversing from read/write to
69 relationships, we can validate the ownership invariant that we expect to hold.
70 If this is violated, it suggests that a use-after-free has happened -- perhaps
77 threats.  This means that for most data, it simply doesn't make sense to use
90 that we're making conscious, considered choices over which zones are made
98 - `zfree_ro`: Free an element back to a read-only zone.  Note that this is a
99   macro that automatically zeroes the pointer after freeing.
100 - `zone_require_ro`: Verify that an element belongs to a given read-only zone
108 Note that `zfree_ro`, `zalloc_ro_mut` and `zalloc_ro_update_elem` will