Hi, On Fri, 5 Aug 2005, Arjan van de Ven wrote: > kcalloc does have value, in that it's a nice api to avoid multiplication > overflows. Just for "1" it's indeed not the most useful API. This would imply a similiar kmalloc() would be useful as well. Second, how relevant is it for the kernel? Is that really the best place to check for rogue user parameters? bye, Roman - 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: kernel: use kcalloc instead kmalloc/memset
- From: "Pekka J Enberg" <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Arjan van de Ven <[email protected]>
- Re: kernel: use kcalloc instead kmalloc/memset
- References:
- [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Pekka Enberg <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Andrew Morton <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Pekka J Enberg <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Andrew Morton <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Roman Zippel <[email protected]>
- Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- From: Arjan van de Ven <[email protected]>
- [PATCH] kernel: use kcalloc instead kmalloc/memset
- Prev by Date: Re: areca-raid-linux-scsi-driver.patch added to -mm tree
- Next by Date: Re: [PATCH 00/14] GFS
- Previous by thread: Re: kernel: use kcalloc instead kmalloc/memset
- Next by thread: Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
- Index(es):
