So why do you complain?
kfree() literally doesn't write to the object.
No, I'm saying that "const" has absolutely *zero* meaning on writes to an
object through _other_ pointers (or direct access) to the object.
And you're seemingly not understanding that *lack* of meaning.
kfree() doesn't do *squat* to the object pointed to by the pointer it is
passed. It only uses it to look up its own data structures, of which the
pointer is but a small detail.
And those other data structures aren't constant.
.. and I'm telling you: kfree() does *nothing* conceptually through that
pointer. No writes, and not even any reads! Which is exactly why it's
const.
The only thing kfree does through that pointer is to update its own
concept of what memory it has free.
Now, what it does to its own free memory is just an implementation detail,
and has nothing what-so-ever to do with the pointer you passed it.
See?
Linus
--
