lkml.org 
[lkml]   [2017]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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@arm.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

\
 
 \ /
  Last update: 2017-09-05 16:40    [W:0.049 / U:2.664 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site