Re: Major slab mem leak with 2.6.17 / GCC 4.1.1

["Catalin Marinas" <catalin.marinas@gmail.com>]

On 13/10/06, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On 10/13/06, nmeyers@vestmark.com <nmeyers@vestmark.com> wrote:
> > If anyone has a version of kmemleak that I can build with 4.1.1, or
> > any other suggestions for instrumentation, I'd be happy to gather more
> > data - the problem is very easy for me to reproduce.
>
> You should cc Catalin for that. Alternatively, you could try
> CONFIG_DEBUG_SLAB_LEAK.

Thanks for cc'ing me (I'm still on holiday and not following the
mailing list). The problem is the __builtin_constant_p gcc function
which doesn't work properly with 4.x versions. It was fixed in latest
gcc versions though. Kmemleak relies on __builtin_constant_p to
determine the pointer aliases and without it you would get plenty of
false positives.

-- 
Catalin