Lines Matching full:shadow

259 granule is encoded in one shadow byte. Those 8 bytes can be accessible,
261 encoding for each shadow byte: 00 means that all 8 bytes of the corresponding
268 In the report above, the arrow points to the shadow byte ``03``, which means
310 Software KASAN modes use shadow memory to record whether each byte of memory is
311 safe to access and use compile-time instrumentation to insert shadow memory
314 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
316 translate a memory address to its corresponding shadow address.
318 Here is the function which translates an address to its corresponding shadow
332 memory accesses are valid or not by checking corresponding shadow memory.
335 directly inserts the code to check shadow memory. This option significantly
349 to store a pointer tag in the top byte of kernel pointers. It uses shadow memory
351 dedicates 1/16th of the kernel memory for shadow memory).
364 emits callbacks to check memory accesses; and inline, which performs the shadow
379 shadow memory.
405 Shadow memory
412 memory to support a real shadow region for every address that could be
413 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
419 By default, architectures only map real memory over the shadow region
422 page is mapped over the shadow area. This read-only shadow page
427 allocator, KASAN temporarily maps real shadow memory to cover them.
432 the kernel will fault when trying to set up the shadow data for stack
443 allocating real shadow memory to back the mappings.
446 page of shadow space. Allocating a full shadow page per mapping would
448 use different shadow pages, mappings would have to be aligned to
453 of the shadow region. This page can be shared by other vmalloc
456 KASAN hooks into the vmap infrastructure to lazily clean up unused shadow
460 that the part of the shadow region that covers the vmalloc space will
461 not be covered by the early shadow page but will be left unmapped.