lkml.org 
[lkml]   [2014]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [RFC/PATCH RESEND -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector.
    Date
    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


    \
     
     \ /
      Last update: 2014-07-10 00:41    [W:4.052 / U:0.820 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site