On Mon, 25 Jun 2007, Christoph Lameter wrote: > On Mon, 25 Jun 2007, Hugh Dickins wrote: > > > > The "sometimes we have kmalloced buffers" locations need to be fixed. > > > > I've said enough, I'd better leave it to others to deter you or not > > from fiddling around pointlessly here. > > Are there any locations left after the two fixes to pa-risc and arm? > > If the ARM fix solves the issue then we may not need that special casing > anymore. Maybe the sometimes has become never? Please reread mails of the last 20 hours. Your "ARM fix" may or may not be a good thing, I don't know. But it had nothing to do with this oops, which (we believe) came from a kmalloc in drivers/mmc/core/sd.c. There are likely to be many other drivers which pass down kmalloc'ed buffers to routines which handle both kmalloc'ed buffers and page buffers. Though very few of those needing to flush_dcache_page. Hugh - 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:
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- References:
- Oops in a driver while using SLUB as a SLAB allocator
- From: Nicolas Ferre <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Linus Torvalds <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Russell King <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Russell King <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Hugh Dickins <[email protected]>
- Re: Oops in a driver while using SLUB as a SLAB allocator
- From: Christoph Lameter <[email protected]>
- Oops in a driver while using SLUB as a SLAB allocator
- Prev by Date: Re: Oops in a driver while using SLUB as a SLAB allocator
- Next by Date: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- Previous by thread: Re: Oops in a driver while using SLUB as a SLAB allocator
- Next by thread: Re: Oops in a driver while using SLUB as a SLAB allocator
- Index(es):