[PATCH RFC] explicit_bzero, again

[Zack Weinberg]

Ping.

On Wed, Sep 9, 2015 at 11:31 AM, Zack Weinberg <zackw@panix.com> wrote:
> This updated patchset adds to the manual discussion of the situation
> where using explicit_bzero *creates* a copy of sensitive data in memory,
> which would not otherwise have been created.  There are no changes to
> the code.  Earlier discussion with Florian and Adhemerval explored some
> possible alternative implementation strategies but reached the
> conclusion that this really is the best we can do without compiler support.
>
> zw