[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807242313.47041.nickpiggin@yahoo.com.au>
Date: Thu, 24 Jul 2008 23:13:46 +1000
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Pekka Enberg <penberg@...helsinki.fi>,
Patrick McHardy <kaber@...sh.net>, Ingo Molnar <mingo@...e.hu>,
David Miller <davem@...emloft.net>, w@....eu,
davidn@...idnewall.com, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, stefanr@...6.in-berlin.de,
rjw@...k.pl, ilpo.jarvinen@...sinki.fi,
Dave Jones <davej@...hat.com>, Matt Mackall <mpm@...enic.com>,
Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [regression] nf_iterate(), BUG: unable to handle kernel NULL pointer dereference
On Thursday 24 July 2008 23:04, Herbert Xu wrote:
> On Thu, Jul 24, 2008 at 10:56:08PM +1000, Nick Piggin wrote:
> > OTOH, skb allocation uses kmalloc don't they? So you could still use
> > SLOB ksize for that I guess.
>
> Yes I was referring to the data portion which is kmalloc'ed.
> That is also why I'm interested in ksize because a priori we
> don't know exactly how big it's going to be. However, we do
> know that statistically 1500 will dominate.
>
> I'm not interested in ksize for kmem_cache at all. So in fact
> we could have something simpler that's based on kmalloc's rounding
> algorithm instead.
Yes you could definitely have a function that returns allocated
bytes for a given kmalloc size. Should be about as fast or faster
than extracting the size from the kaddr...
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists