linux-kernel - Re: kmemleak not always catching stuff

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 5 Sep 2017 15:39:51 +0100
From:   Catalin Marinas <catalin.marinas@....com>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        kasan-dev <kasan-dev@...glegroups.com>
Subject: Re: kmemleak not always catching stuff

On Tue, Sep 05, 2017 at 04:23:47PM +0200, Dmitry Vyukov wrote:
> On Mon, Sep 4, 2017 at 12:09 PM, Catalin Marinas
> <catalin.marinas@....com> wrote:
> > I also need to find
> > some time to implement a "stopscan" command which uses stop_machine()
> > and skips the heuristics for reducing false positives.
> 
> "stopscan" would be great. We would like to deploy continuous testing
> with kmemleak, but while it has systematic false positives, it is not
> possible. Performance kinda matters, but only when a tool does not
> have false positives. We probably will just not enable it on all
> machines (it introduces significant slowdown even today).

The downside is that scanning may take minutes. I would expect some RCU
warnings once scanning is done.

-- 
Catalin