Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub

From: Srihari Vijayaraghavan
Date: Fri May 25 2007 - 22:49:44 EST


--- Christoph Lameter <clameter@xxxxxxx> wrote:
> I finally figured out the second issue. Took some time to get that figure
> out. Sorry. But now all the bug reports make sense.

[...]

Impressive Christoph. Indeed, this fixes my problem on latest -git (its hg
equivalent :-)). Well done.

(Tested with CONFIG_SLAB_DEBUG without slub_debug; all was well. Then with
slub_debug & slabinfo -v also; again all was well. I had many LOCKDEP and its
relatives also compiled in.)

Now hoping it'll be in 2.6.22-rc3 :-)).

> Signed-off-by: Christoph Lameter <clameter@xxxxxxx>
>
> ---
> mm/slub.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> Index: slub/mm/slub.c
> ===================================================================
> --- slub.orig/mm/slub.c 2007-05-25 18:28:42.000000000 -0700
> +++ slub/mm/slub.c 2007-05-25 18:29:46.000000000 -0700
> @@ -2473,6 +2473,7 @@ void __init kmem_cache_init(void)
> */
> create_kmalloc_cache(&kmalloc_caches[0], "kmem_cache_node",
> sizeof(struct kmem_cache_node), GFP_KERNEL);
> + kmalloc_caches[0].refcount = -1;
> #endif
>
> /* Able to allocate the per node structures */
> @@ -2520,6 +2521,12 @@ static int slab_unmergeable(struct kmem_
> if (s->ctor)
> return 1;
>
> + /*
> + * We may have set a slab to be unmergeable during bootstrap.
> + */
> + if (s->refcount < 0)
> + return 1;
> +
> return 0;
> }



___________________________________________________________________________________
How would you spend $50,000 to create a more sustainable environment in Australia? Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

-
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/