On Tue, 7 Mar 2006, Pekka J Enberg wrote: > > No you're not, it's broken. However, I think you're forgetting to reset > cachep->num when we go over MAX_GFP_ORDER, no? No, we only ever set "cachep->num" for something that we've decided is valid. "gfporder" can never be > MAX_GFP_ORDER inside the loop, because we just iterate between 0..MAX_GFP_ORDER. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Slab corruption in 2.6.16-rc5-mm2
- From: Jesper Juhl <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Linus Torvalds <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Linus Torvalds <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Jesper Juhl <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: "Jesper Juhl" <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: "Jesper Juhl" <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Linus Torvalds <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: "Jesper Juhl" <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Linus Torvalds <[email protected]>
- Re: Slab corruption in 2.6.16-rc5-mm2
- From: Linus Torvalds <[email protected]>
- [PATCH] slab: fix offslab_limit in calculate_slab_order (Was: Slab corruption in 2.6.16-rc5-mm2)
- From: Pekka J Enberg <[email protected]>
- Slab corruption in 2.6.16-rc5-mm2
- Prev by Date: Re: 2.6.16-rc5-mm2: IPW_QOS: two remarks
- Next by Date: 2.6.15-rt20 compilation errors
- Previous by thread: [PATCH] slab: fix offslab_limit in calculate_slab_order (Was: Slab corruption in 2.6.16-rc5-mm2)
- Next by thread: Re: [PATCH] slab: fix offslab_limit in calculate_slab_order (Was: Slab corruption in 2.6.16-rc5-mm2)
- Index(es):
 |