[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706221021540.16991@schroedinger.engr.sgi.com>
Date: Fri, 22 Jun 2007 10:26:52 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Hugh Dickins <hugh@...itas.com>,
Nicolas Ferre <nicolas.ferre@....atmel.com>,
ARM Linux Mailing List
<linux-arm-kernel@...ts.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Marc Pignat <marc.pignat@...s.ch>,
Andrew Victor <andrew@...people.com>,
Pierre Ossman <drzeus@...eus.cx>,
Andrew Morton <akpm@...ux-foundation.org>,
Russell King <rmk@....linux.org.uk>
Subject: Re: Oops in a driver while using SLUB as a SLAB allocator
On Fri, 22 Jun 2007, Linus Torvalds wrote:
> > Looks like it would indeed address the immediate issue on ARM -
> > IF they've no particular reason to be using kmalloc there.
>
> I think the right thing to do is do both of these things. I already
> applied Hugh's patch - it seemed like a total nobrainer to do at this
> stage in the 2.6.22 -rc series. But that doesn't mean that we should not
> _also_ look at "flush_dcache_page()" users.
Hugh's patch not address the complete issue. It only works right now
because the size of the allocation is page size and fits right into a slab
page. If debugging is enabled then the slab size will increase and the
"pages" will be misaligned which will lead to other sorts of funky
behavior. kmalloc allocations are only guaranteed to be aligned to
ARCH_KMALLOC_MINALIGN which is 4 to 8 bytes. If one must have a
page aligned entity out of a slab allocator then a custom slab needs to be
created.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists