[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48EB6D2C.30806@linux-foundation.org>
Date: Tue, 07 Oct 2008 09:07:40 -0500
From: Christoph Lameter <cl@...ux-foundation.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC: Matt Mackall <mpm@...enic.com>, linux-mm <linux-mm@...ck.org>,
Nick Piggin <nickpiggin@...oo.com.au>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] SLOB's krealloc() seems bust
> Which basically shows us that the content of the pcpu_size[] array got
> corrupted after the krealloc() call in split_block().
>
> Which made me look at which slab allocator I had selected, which turned
> out to be SLOB (from testing the network swap stuff).
krealloc() is in generic core code (mm/util.c) and is the same for all allocators.
krealloc uses ksize() which is somewhat dicey for SLOB because it only works
on kmalloc'ed memory. Is the krealloc used on memory allocated with kmalloc()?
Slob's ksize could use a BUG_ON for the case in which ksize() is used on
kmem_cache_alloc'd memory.
/* can't use ksize for kmem_cache_alloc memory, only kmalloc */
size_t ksize(const void *block)
{
struct slob_page *sp;
BUG_ON(!block);
if (unlikely(block == ZERO_SIZE_PTR))
return 0;
sp = (struct slob_page *)virt_to_page(block);
Add a BUG_ON(!kmalloc_cache(sp))?
if (slob_page(sp))
return ((slob_t *)block - 1)->units + SLOB_UNIT;
^^^^^^^ Is this correct?
else
return sp->page.private;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists