#2 Using kzfree() to clear specific bits of memory (and I question theWell, yes, that's what kzfree() needs to do given the current API. I
kzfree implementation as it seems ksize can return numbers much much
bigger than the allocated space you need to clear - correct but oversize)
or using other flags. I'd favour kzfree personally (and fixing it to work
properly)
am not sure why you think it's a problem, though. Adding a size
argument to the function will make it more error prone.
Definitely - am I right however that
x = kzalloc(size, flags)
blah
kzfree(x)
can memset a good deal more memory (still safely) than "size" to zero ?
That has performance relevance if so and it ought to at least be
documented.