lkml.org 
[lkml]   [2005]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] kernel: use kcalloc instead kmalloc/memset
Hi,

On Fri, 5 Aug 2005, Arjan van de Ven wrote:

> > > we've had a non-negliable amount of security holes because of this
> >
> > So why don't we have a similiar kmalloc()?
>
> nope kmalloc is not an array allocator
>
> > > it makes it easy and safe. Of course you can and should check it in all
> > > users. Just that using a safer API is generally better than forcing
> > > everyone to do it themselves.
> >
> > How exactly does this make it a "safe API"? Even if it checks for this one
> > case, it still makes the user suspectible for allocating big amounts of
> > unswappable memory.
>
> 128Kb max.

You completely missed the point and didn't answer my questions at all... :-(

bye, Roman
-
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: 2005-08-05 13:00    [W:0.141 / U:0.844 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site