Lines Matching full:shadow

256 granule is encoded in one shadow byte. Those 8 bytes can be accessible,
258 encoding for each shadow byte: 00 means that all 8 bytes of the corresponding
265 In the report above, the arrow points to the shadow byte ``03``, which means
307 Software KASAN modes use shadow memory to record whether each byte of memory is
308 safe to access and use compile-time instrumentation to insert shadow memory
311 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
313 translate a memory address to its corresponding shadow address.
315 Here is the function which translates an address to its corresponding shadow
329 memory accesses are valid or not by checking corresponding shadow memory.
332 directly inserts the code to check shadow memory. This option significantly
346 to store a pointer tag in the top byte of kernel pointers. It uses shadow memory
348 dedicates 1/16th of the kernel memory for shadow memory).
361 emits callbacks to check memory accesses; and inline, which performs the shadow
376 shadow memory.
402 Shadow memory
409 memory to support a real shadow region for every address that could be
410 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
416 By default, architectures only map real memory over the shadow region
419 page is mapped over the shadow area. This read-only shadow page
424 allocator, KASAN temporarily maps real shadow memory to cover them.
429 the kernel will fault when trying to set up the shadow data for stack
440 allocating real shadow memory to back the mappings.
443 page of shadow space. Allocating a full shadow page per mapping would
445 use different shadow pages, mappings would have to be aligned to
450 of the shadow region. This page can be shared by other vmalloc
453 KASAN hooks into the vmap infrastructure to lazily clean up unused shadow
457 that the part of the shadow region that covers the vmalloc space will
458 not be covered by the early shadow page but will be left unmapped.