Lines Matching full:shadow

150 granule is encoded in one shadow byte. Those 8 bytes can be accessible,
152 encoding for each shadow byte: 00 means that all 8 bytes of the corresponding
159 In the report above, the arrow points to the shadow byte ``03``, which means
215 Software KASAN modes use shadow memory to record whether each byte of memory is
216 safe to access and use compile-time instrumentation to insert shadow memory
219 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
221 translate a memory address to its corresponding shadow address.
223 Here is the function which translates an address to its corresponding shadow
237 memory accesses are valid or not by checking corresponding shadow memory.
240 directly inserts the code to check shadow memory. This option significantly
254 to store a pointer tag in the top byte of kernel pointers. It uses shadow memory
256 dedicates 1/16th of the kernel memory for shadow memory).
269 emits callbacks to check memory accesses; and inline, which performs the shadow
287 shadow memory.
316 Shadow memory
321 memory to support a real shadow region for every address that could be
322 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
328 By default, architectures only map real memory over the shadow region
331 page is mapped over the shadow area. This read-only shadow page
336 allocator, KASAN temporarily maps real shadow memory to cover them.
341 the kernel will fault when trying to set up the shadow data for stack
352 allocating real shadow memory to back the mappings.
355 page of shadow space. Allocating a full shadow page per mapping would
357 use different shadow pages, mappings would have to be aligned to
362 of the shadow region. This page can be shared by other vmalloc
365 KASAN hooks into the vmap infrastructure to lazily clean up unused shadow
369 that the part of the shadow region that covers the vmalloc space will
370 not be covered by the early shadow page but will be left unmapped.