Re: Re: Re: Re: [Oops] i386 mm/slab.c (cache_flusharray)

[pinotj]

>De: Linus Torvalds <torvalds@xxxxxxxx>
>On Thu, 27 Nov 2003 pinotj@xxxxxxxxxxxxxxxx wrote:
>>
>> Here is the result of test of 2.6.0-test10 with the printk patch in
>> slab.c and this new patch for fork.c from Linus :
>
>The fork.c change can really only affect threaded programs using the new
>threading, and even then is likely to hit only in very unlikely
>circumstances. Certainly not a kernel compile.
>
>I'm wondering if the slab debugging code is just broken somehow. If you
>have lots of memory, it should even work for you.
>
>NOTE! For this patch to make sense, you have to enable the page allocator
>debugging thing (CONFIG_DEBUG_PAGEALLOC), and you have to live with the
>fact that it wastes a _lot_ of memory.
>
>There's another problem with this patch: if the bug is actually in the
>slab code itself, this will obviously not find it, since it disables that
>code entirely.
>
>		Linus
[patch]

Thanks. I will try this.
I have 256MB RAM and I always test with very few process running so I think it will not be a problem.

Jerome

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