Lines Matching refs: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
218 Software KASAN modes use shadow memory to record whether each byte of memory is
219 safe to access and use compile-time instrumentation to insert shadow memory
222 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
224 translate a memory address to its corresponding shadow address.
226 Here is the function which translates an address to its corresponding shadow
240 memory accesses are valid or not by checking corresponding shadow memory.
243 directly inserts the code to check shadow memory. This option significantly
257 to store a pointer tag in the top byte of kernel pointers. It uses shadow memory
259 dedicates 1/16th of the kernel memory for shadow memory).
272 emits callbacks to check memory accesses; and inline, which performs the shadow
290 shadow memory.
324 memory to support a real shadow region for every address that could be
325 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
331 By default, architectures only map real memory over the shadow region
334 page is mapped over the shadow area. This read-only shadow page
339 allocator, KASAN temporarily maps real shadow memory to cover them.
344 the kernel will fault when trying to set up the shadow data for stack
355 allocating real shadow memory to back the mappings.
358 page of shadow space. Allocating a full shadow page per mapping would
360 use different shadow pages, mappings would have to be aligned to
365 of the shadow region. This page can be shared by other vmalloc
368 KASAN hooks into the vmap infrastructure to lazily clean up unused shadow
372 that the part of the shadow region that covers the vmalloc space will
373 not be covered by the early shadow page but will be left unmapped.