lkml.org 
[lkml]   [2008]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [regression] nf_iterate(), BUG: unable to handle kernel NULL pointer dereference
From
Date
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.

On Thursday 24 July 2008 23:04, Herbert Xu wrote:
> > 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.

On Thu, 2008-07-24 at 23:13 +1000, Nick Piggin wrote:
> 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...

Yup, makes sense.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2008-07-24 15:35    [W:0.265 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site