lkml.org 
[lkml]   [2005]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Patch for slab leak debugging
From
Date
> >Yeah I knew there was one, but I thought that was a standalone patch
> >(the one turning all bufctl to unsigned long, turning off irqs and
> >printing all slabs_full to console), my intention with this was a
> >proper /proc entry, something that could be a simple config option.
> >
> >
> >
> No, I never wrote a proper /proc interface. But I think the bufctl
> approach is the better solution than storing the first 5 entries in the
> slab structure:
> What if there is a leak on a cache with more than 5 entries per slab?

As slab leaks usually go out of control I think it will be enough to
show what is leaking anyway, but you're right on the bufctl approach I
think. I may have misundersood the bufctl thing a bit before doing this.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-07-09 12:30    [W:0.077 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site