[PATCH] Add RTLD_RELOAD to dlopen

Florian Weimer fweimer@redhat.com
Thu Aug 3 17:26:00 GMT 2017


On 08/03/2017 04:37 PM, Samuel Thibault wrote:
> Hello,
> 
> So, is it OK to add this? Considering that dlmopen() brings us far from
> enough factorization for our needs, and dlopen() currently never reloads
> unless a real fat copy of the file is done (hardlinks/symlinks don't
> work, as it is based on st_ino).

I would still see a discussion of the intended symbol binding behavior.

What happens if a subsequently loaded object references a duplicated
library?  Will it reference the most recent duplicate, or the original
library?

What happens if libA depends on libB, and you need to duplicate both?

What happens with RTLD_NEXT in a duplicated object?  Will it look at
earlier duplicates, too?

What happens if you reload libc.so?  Your test case assumes that
reloading works for libm.so, but I think even that is a bit of a stretch.

Thanks,
Florian



More information about the Libc-alpha mailing list