On Fri, 2009-07-17 at 18:32 +1000, Michael Ellerman wrote: > On Fri, 2009-07-17 at 09:26 +0100, Catalin Marinas wrote: > > On Fri, 2009-07-17 at 10:29 +1000, Michael Ellerman wrote: > > > The wrinkle is that lmb never frees, so by definition it can't leak :) > > > > You can pass min_count = 0 to kmemleak_alloc() so that it would never > > report such blocks as leaks (see the alloc_bootmem hooks). > > OK. I couldn't see any description of what min_count meant anywhere,
There isn't any, indeed. I'll try to add some description to the kmemleak api. But it basically means the minimum number a pointer value should be found during scanning so that it is not reported as a leak. If this value is 0, it would never be reported. The kmalloc/kmem_cache_alloc have this value 1 and vmalloc is higher because of other structures like vm_area holding pointers o the same block. -- Catalin _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
