Re: CONFIG_DEBUG_SLAB_LEAK omits size-4096 and larger?

From: J. Bruce Fields
Date: Wed Jun 11 2008 - 18:54:44 EST


On Wed, Jun 11, 2008 at 05:46:13PM -0500, Weathers, Norman R. wrote:
> I will try and get it patched and retested, but it may be a day or two
> before I can get back the information due to production jobs now
> running. Once they finish up, I will get back with the info.

Understood.

> Thanks everyone for looking at this, by the way!

And thanks for your persistence.

--b.

>
> >
> >
> > diff --git a/mm/slab.c b/mm/slab.c
> > index 06236e4..b379e31 100644
> > --- a/mm/slab.c
> > +++ b/mm/slab.c
> > @@ -2202,7 +2202,7 @@ kmem_cache_create (const char *name,
> > size_t size, size_t align,
> > * above the next power of two: caches with object
> > sizes just above a
> > * power of two have a significant amount of internal
> > fragmentation.
> > */
> > - if (size < 4096 || fls(size - 1) == fls(size-1 + REDZONE_ALIGN +
> > + if (size < 8192 || fls(size - 1) == fls(size-1 + REDZONE_ALIGN +
> > 2 *
> > sizeof(unsigned long long)))
> > flags |= SLAB_RED_ZONE | SLAB_STORE_USER;
> > if (!(flags & SLAB_DESTROY_BY_RCU))
> >
>
>
> Norman Weathers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/