Lines Matching defs:shadow
3 * This file contains KASAN runtime code that manages shadow memory for
132 * Perform shadow offset calculation based on untagged address, as
161 u8 *shadow = (u8 *)kasan_mem_to_shadow(addr + size);
162 *shadow = size & KASAN_GRANULE_MASK;
172 * Perform shadow offset calculation based on untagged address, as
254 * If shadow is mapped already than it must have been mapped
279 * In the latter case we can use vfree() to free shadow.
283 * Currently it's not possible to free shadow mapped
356 * User Mode Linux maps enough shadow memory for all of virtual memory
392 * STORE shadow(a), unpoison_val
394 * STORE shadow(a+99), unpoison_val x = LOAD p
396 * STORE p, a LOAD shadow(x+99)
398 * If there is no barrier between the end of unpoisoning the shadow
401 * poison in the shadow.
407 * get_vm_area() and friends, the caller gets shadow allocated but
446 * That might not map onto the shadow in a way that is page-aligned:
456 * |??AAAAAA|AAAAAAAA|AA??????| < shadow
460 * shadow of the region aligns with shadow page boundaries. In the
461 * example, this gives us the shadow page (2). This is the shadow entirely
465 * partially covered shadow pages - (1) and (3) in the example. For this,
478 * |FFAAAAAA|AAAAAAAA|AAF?????| < shadow
482 * the free region down so that the shadow is page aligned. So we can free
505 * means that so long as we are careful with alignment and only free shadow
583 * Poison the shadow for a vmalloc region. Called as part of the