On 07/14/14 13:58, Peter Zijlstra wrote: > On Mon, Jul 14, 2014 at 01:34:40PM +0400, Andrey Ryabinin wrote: >> On 07/14/14 13:04, Peter Zijlstra wrote: >>> On Sun, Jul 13, 2014 at 07:45:56PM -0400, Sasha Levin wrote: >>>> On 07/13/2014 05:51 PM, Sasha Levin wrote: >>>>> Hi all, >>>>> >>>>> While fuzzing with trinity inside a KVM tools guest running the latest >>>>> -next >>>>> kernel with the KASAN patchset, I've stumbled on the following spew: >>> >>> WTH is a KASAN? >>> >> >> It's dynamic memory checker, detects use after free, out of bounds accesses >> - https://lkml.org/lkml/2014/7/9/990 > > How is it better/different from the existing use after free stuff? That > email fails to tell me. >
DEBUG_PAGEALLOC works on page-granularity level, kasan can do checks at sub-page granularity (for slab objects). SLUB_DEBUG(poisoning, etc.) doesn't guarantee that you will catch use-after-free. For example if you are only reading and checking a single bit in some already free object. Kasan will catch this. KASAN is very similar to kmemcheck, but definitely faster. The only thing that currently kasan can't catch, while kmemcheck can - is reads of uninitialized memory. -- 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/
