Re: [RFC/PATCH RESEND -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector.

From: Vegard Nossum
Date: Wed Jul 09 2014 - 17:59:11 EST

On 9 July 2014 23:44, Andi Kleen <andi@xxxxxxxxxxxxxx> wrote:
> Dave Hansen <dave.hansen@xxxxxxxxx> writes:
>> You're also claiming that "KASAN is better than all of
> better as in finding more bugs, but surely not better as in
> "do so with less overhead"
>> CONFIG_DEBUG_PAGEALLOC". So should we just disallow (or hide)
>> DEBUG_PAGEALLOC on kernels where KASAN is available?
> I don't think DEBUG_PAGEALLOC/SLUB debug and kasan really conflict.
> DEBUG_PAGEALLOC/SLUB is "much lower overhead but less bugs found".
> KASAN is "slow but thorough" There are niches for both.
> But I could see KASAN eventually deprecating kmemcheck, which
> is just incredible slow.

FWIW, I definitely agree with this -- if KASAN can do everything that
kmemcheck can, it is no doubt the right way forward.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at