On Thu, Nov 27, 2014 at 04:00:54PM +0000, Andrey Ryabinin wrote: > kmalloc internally round up allocation size, and kmemleak > uses rounded up size as object's size. This makes kasan > to complain while kmemleak scans memory or calculates of object's > checksum. The simplest solution here is to disable kasan.
This would indeed be the simplest since by the time kmemleak callbacks get called (from slub) we lose the original size information (especially for kmem_cache_alloc). > Signed-off-by: Andrey Ryabinin <a.ryabi...@samsung.com> > --- > mm/kmemleak.c | 6 ++++++ > 1 file changed, 6 insertions(+) Acked-by: Catalin Marinas <catalin.mari...@arm.com> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
