Re: 2.6.23 compile failure - slab/slob interspanking

[Matt Mackall <mpm@selenic.com>]

On Wed, Jul 18, 2007 at 09:18:36AM +0900, Paul Mundt wrote:
> On Tue, Jul 17, 2007 at 10:00:08PM +0200, Jan Engelhardt wrote:
> > 81cda6626178cd55297831296ba8ecedbfd8b52d is first bad commit
> > commit 81cda6626178cd55297831296ba8ecedbfd8b52d
> > Author: Christoph Lameter <clameter@sgi.com>
> > Date:   Tue Jul 17 04:03:29 2007 -0700
> > 
> >     Slab allocators: Cleanup zeroing allocations
> >     
> >     It becomes now easy to support the zeroing allocs with generic inline
> >     functions in slab.h.  Provide inline definitions to allow the continued use of
> >     kzalloc, kmem_cache_zalloc etc but remove other definitions of zeroing
> >     functions from the slab allocators and util.c.
> >     
> >     Signed-off-by: Christoph Lameter <clameter@sgi.com>
> >     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> >     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> > 
> This fixes it for me with your .config:
> 
> slob: Kill off duplicate kzalloc() definition.
> 
> With the slab zeroing allocations cleanups Christoph stubbed in a generic
> kzalloc(), which was missed on SLOB. Follow the SLAB/SLUB changes and
> kill off the __kzalloc() wrapper that SLOB was using.

Looks fine to me.

> Reported-by: Jan Engelhardt <jengelh@computergmbh.de>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>

Signed-off-by: Matt Mackall <mpm@selenic.com>

-- 
Mathematics is the supreme nostalgia of our time.