Lines Matching full:shadow

233 granule is encoded in one shadow byte. Those 8 bytes can be accessible,
235 encoding for each shadow byte: 00 means that all 8 bytes of the corresponding
242 In the report above, the arrow points to the shadow byte ``03``, which means
263 Software KASAN modes use shadow memory to record whether each byte of memory is
264 safe to access and use compile-time instrumentation to insert shadow memory
267 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
269 translate a memory address to its corresponding shadow address.
271 Here is the function which translates an address to its corresponding shadow
285 memory accesses are valid or not by checking corresponding shadow memory.
288 directly inserts the code to check shadow memory. This option significantly
302 to store a pointer tag in the top byte of kernel pointers. It uses shadow memory
304 dedicates 1/16th of the kernel memory for shadow memory).
317 emits callbacks to check memory accesses; and inline, which performs the shadow
332 shadow memory.
358 Shadow memory
365 memory to support a real shadow region for every address that could be
366 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
372 By default, architectures only map real memory over the shadow region
375 page is mapped over the shadow area. This read-only shadow page
380 allocator, KASAN temporarily maps real shadow memory to cover them.
385 the kernel will fault when trying to set up the shadow data for stack
396 allocating real shadow memory to back the mappings.
399 page of shadow space. Allocating a full shadow page per mapping would
401 use different shadow pages, mappings would have to be aligned to
406 of the shadow region. This page can be shared by other vmalloc
409 KASAN hooks into the vmap infrastructure to lazily clean up unused shadow
413 that the part of the shadow region that covers the vmalloc space will
414 not be covered by the early shadow page but will be left unmapped.