[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 17 Jul 2007 19:49:21 -0500
From: Matt Mackall <mpm@...enic.com>
To: Paul Mundt <lethal@...ux-sh.org>,
Jan Engelhardt <jengelh@...putergmbh.de>, clameter@....com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 2.6.23 compile failure - slab/slob interspanking
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@....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@....com>
> > Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> > Signed-off-by: Linus Torvalds <torvalds@...ux-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@...putergmbh.de>
> Signed-off-by: Paul Mundt <lethal@...ux-sh.org>
Signed-off-by: Matt Mackall <mpm@...enic.com>
--
Mathematics is the supreme nostalgia of our time.
-
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