On 09/04/2015 03:49 PM, Jakub Jelinek wrote:
Clearly it is used by some programs, so it should be considered part
of the
public API. If it wasn't meant to be exported, it should not have been
exported. The ld.so warning is only emitted if there is a copy relocation
against that symbol and the symbol has different size in the copy relocation
vs. the new size in the shared library.
Ugh, I forgot.
Will the process use the size from the shared library, or will the
object be truncated, so that when the library tries to traverse the
array (using its hard-coded size), it will read past the end of the
allocated portion?
--
Florian Weimer / Red Hat Product Security