Messages in this thread | | | From | Andi Kleen <> | Subject | Re: [RFC/PATCH RESEND -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector. | Date | Wed, 09 Jul 2014 14:44:56 -0700 |
| |
Dave Hansen <dave.hansen@intel.com> 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.
-Andi
-- ak@linux.intel.com -- Speaking for myself only
| |