Lines Matching full:memory

7 KernelAddressSANitizer (KASAN) is a dynamic memory error detector designed to
13 memory access, and therefore requires a compiler version that supports that.
41 Both KASAN modes work with both SLUB and SLAB memory allocators.
125     Memory state around the buggy address:
136 access, a stack trace of where the accessed memory was allocated (in case bad
139 the accessed slab object and information about the accessed memory page.
141 In the last section the report shows memory state around the accessed address.
144 The state of each 8 aligned bytes of memory is encoded in one shadow byte.
147 of the corresponding memory region are accessible; number N (1 <= N <= 7) means
151 inaccessible memory like redzones or freed memory (see mm/kasan/kasan.h).
156 For tag-based KASAN this last report section shows the memory tags around the
166 From a high level, our approach to memory error detection is similar to that
167 of kmemcheck: use shadow memory to record whether each byte of memory is safe
169 memory on each memory access.
171 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (e.g. 16TB
173 translate a memory address to its corresponding shadow address.
186 Compile-time instrumentation is used to insert memory access checks. Compiler
188 memory access of size 1, 2, 4, 8 or 16. These functions check whether memory
189 access is valid or not by checking corresponding shadow memory.
192 function calls GCC directly inserts the code to check the shadow memory.
201 uses shadow memory to store memory tags associated with each 16-byte memory
202 cell (therefore it dedicates 1/16th of the kernel memory for shadow memory).
204 On each memory allocation tag-based KASAN generates a random tag, tags the
205 allocated memory with this tag, and embeds this tag into the returned pointer.
207 before each memory access. These checks make sure that tag of the memory that
209 memory. In case of a tag mismatch tag-based KASAN prints a bug report.
212 emits callbacks to check memory accesses; and inline, that performs the shadow
213 memory checks inline). With outline instrumentation mode, a bug report is
219 use hardware memory tagging support instead of compiler instrumentation and
220 manual shadow memory manipulation.