Messages in this thread Patch in this message | | | Date | Wed, 14 Jan 2009 00:17:45 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH] lib/idr.c: Zero memory properly in idr_remove_all |
| |
On Wed, 14 Jan 2009 09:19:01 +0200 "Pekka Enberg" <penberg@cs.helsinki.fi> wrote:
> On Wed, Jan 14, 2009 at 12:48 AM, Andrew Morton > <akpm@linux-foundation.org> wrote: > >> If the idr code passes uninitialized objects to kmem_cache_free(), then > >> the next kmem_cache_alloc will return a bad object. > >> > > > > None of this got us much closer to fixing the bug ;) > > > > What do we think of just removing the constructor and using > > kmem_cache_zalloc()? > > Why do I get the feeling that we have merged a similar patch before?
Dunno - maybe we had the same bug in other places.
> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Here 'tis:
From: Andrew Morton <akpm@linux-foundation.org>
David points out that the idr_remove_all() function returns unused slabs to the kmem cache, but needs to zero them first or else they will be uninitialized upon next use. This causes crashes which have been observed in the firewire subsystem.
He fixed this by zeroing the object before freeing it in idr_remove_all().
But we agree that simply removing the constructor and zeroing the object at allocation time is simpler than relying upon slab constructor machinery and might even be faster.
This problem was introduced by
commit cf481c20c476ad2c0febdace9ce23f5a4db19582 Author: Nadia Derbey <Nadia.Derbey@bull.net> AuthorDate: Fri Jul 25 01:48:02 2008 -0700 Commit: Linus Torvalds <torvalds@linux-foundation.org> CommitDate: Fri Jul 25 10:53:42 2008 -0700
idr: make idr_remove rcu-safe
which was first released in 2.6.27.
There are no known codesites which trigger this bug in 2.6.27 or 2.6.28. The post-2.6.28 firewire changes are the only known triggerer.
There might of course be not-yet-discovered triggerers in 2.6.27 and 2.6.28, and there might be out-of-tree triggerers which are added to those kernel versions. I'll let the -stable guys decide whether they want to backport this fix.
Reported-by: David Moore <dcm@acm.org> Cc: Stefan Richter <stefanr@s5r6.in-berlin.de> Cc: Nadia Derbey <Nadia.Derbey@bull.net> Cc: Paul E. McKenney <paulmck@us.ibm.com> Cc: Manfred Spraul <manfred@colorfullife.com> Cc: Kristian Hgsberg <krh@redhat.com> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> ---
lib/idr.c | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-)
diff -puN lib/idr.c~lib-idrc-use-kmem_cache_zalloc-for-the-idr_layer-cache lib/idr.c --- a/lib/idr.c~lib-idrc-use-kmem_cache_zalloc-for-the-idr_layer-cache +++ a/lib/idr.c @@ -121,7 +121,7 @@ int idr_pre_get(struct idr *idp, gfp_t g { while (idp->id_free_cnt < IDR_FREE_MAX) { struct idr_layer *new; - new = kmem_cache_alloc(idr_layer_cache, gfp_mask); + new = kmem_cache_zalloc(idr_layer_cache, gfp_mask); if (new == NULL) return (0); move_to_free_list(idp, new); @@ -623,16 +623,10 @@ void *idr_replace(struct idr *idp, void } EXPORT_SYMBOL(idr_replace); -static void idr_cache_ctor(void *idr_layer) -{ - memset(idr_layer, 0, sizeof(struct idr_layer)); -} - void __init idr_init_cache(void) { idr_layer_cache = kmem_cache_create("idr_layer_cache", - sizeof(struct idr_layer), 0, SLAB_PANIC, - idr_cache_ctor); + sizeof(struct idr_layer), 0, SLAB_PANIC, NULL); } /** _
| |