[PATCH 09/30] mtd: Don't cast kmalloc() return value in drivers/mtd/maps/pmcmsp-flash.c

[Kyle Moffett]

On Aug 25, 2007, at 20:36:32, Jesper Juhl wrote:
> On 26/08/07, Robert P. J. Day <rpjday at mindspring.com> wrote:
>> technically, nothing.  but if you're not going to use kcalloc()  
>> when you're explicitly allocating an array of identical objects  
>> (that you want zero-filled, as a bonus), then what's the point of  
>> ever having defined a kcalloc() routine in the first place?
>>
> I wonder a bit about that myself...
>
> I have found some other issues in that function that I want to fix,  
> so I'll be respinning the patch as a patch series instead - and why  
> not; I'll just go with kcalloc() and see what the maintainers have  
> to say, it's not like I personally care much one way or the other.

I think the original reasoning behind kcalloc() was that it did some  
extra input checking, so that if the product of the two numbers  
overflowed, it would fail with NULL instead of allocating  
insufficient space.  In the kernel it doesn't matter in practice  
since you MUST have additional checking on the size of allocated  
memory anyways, not even considering the fact that >PAGE_SIZE  
allocations are probably going to fail with decent frequency regardless.

Cheers,
Kyle Moffett