[PATCH 0/3] explicit_bzero v5

[Paul Eggert]

On 11/15/2016 07:55 AM, Zack Weinberg wrote:
> Paul Eggert also observed that a call to explicit_bzero might expose
> the_address_  of a buffer containing sensitive data, and perhaps
> another thread could exfiltrate the data before it was erased.
> I thought about it and I have concluded that this, like the other
> remaining problems with this API, needs to be addressed in the
> compiler

That sounds reasonable. Could you please document this, though? Perhaps 
something like the following, after the paragraph about copying objects?


@strong{Warning:} Calling @code{explicit_bzero} may expose
the object's address to other parts of the program, defeating
address space layout randomization.