On Thu, Nov 28, 2013 at 03:13:53PM +0000, jb wrote:
j> > But I don't understand why you find ksize()/malloc_usable_size() dangerous.
j> > ...
j> The original crime is commited when *usable size* (an implementation detail)
j> is exported (leaked) to the caller.
j> To be blunt, when a caller requests memory of certain size, and its request
j> satisfied, then it is not its business to learn details beyond that (and they
j> should not be offered as well).
j> The API should be sanitized, in kernel and user space.
j> Otherwise, all kind of charlatans will try to play hair-raising games with
j> If the caller wants to track the *requested size* programmatically, it is its
j> business to do it and it can be done very easily.
This is kind of APIs that just shouldn't exist.
Totus tuus, Glebius.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"