[PATCH 0/3] explicit_bzero v5

[Zack Weinberg]

On 11/16/2016 09:58 AM, Andreas Schwab wrote:
> On Nov 16 2016, Zack Weinberg <zackw@panix.com> wrote:
> 
>> This doesn't fully resolve the question in my head, though.  The case
>> we're discussing is an impl-namespace symbol __explicit_bzero, which is
>> functionally identical to a public symbol explicit_bzero, and not
>> expected ever to change its behavior.  It exists, as far as I
>> understand, _solely_ so that uses of this symbol in libcrypt.so will
>> resolve to the definition in libc.so even if other objects in the link
>> interpose on the public symbol.
> 
> It's a public symbol, so it gets a public version.  It does not matter
> whether the reference is created explicitly or implicitly.

It is not obvious to me that it is a public symbol.  Please explain
exactly what your criteria are for declaring it a public symbol.

zw