On 17 November 2015 at 16:20, Andrey Ryabinin <[email protected]> wrote: > kasan_module_alloc() allocates shadow memory for module and frees it on module > unloading. It doesn't store the pointer to allocated shadow memory because > it could be calculated from the shadowed address, i.e. > kasan_mem_to_shadow(addr). > Since kmemleak cannot find pointer to allocated shadow, it thinks that memory > leaked. > We should tell kmemleak that this is not a leak. [...] > @@ -444,6 +445,7 @@ int kasan_module_alloc(void *addr, size_t size) > > if (ret) { > find_vm_area(addr)->flags |= VM_KASAN; > + kmemleak_not_leak(ret); > return 0; > }
If such memory does not contain any pointers to other objects, you could use kmemleak_ignore() which would make kmemleak not scan it at all (slight performance improvement). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
