Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 25 May 2020 20:26:51 +0300
From: Alexander Scherbatiy <>
To: Rich Felker <>
Cc:, Markus Wichmann <>
Subject: Re: Shared library loading

On 22.05.2020 21:25, Rich Felker wrote:

> The concept here is that non-pathname library names should be loaded
> from the library path and not replaced by something (typically a
> "module" or "plug-in") in a different, explicitly-loaded location that
> happens to have a colliding base filename.
> For example suppose your application loads modules from $libdir/myapp/
> and has a module named "". Unbeknownst to you, there's also a
> "" in the system paths, and some library you potentially load
> indirectly (maybe the GPU driver for some video hardware you've never
> heard of) depends on "".
> If dlopen("$libdir/myapp/") had put "" in the
> namespace such that it would satisfy future load requests for the name
> "", the subsequent load would break due to getting the wrong
> (unrelated) library.
   Is it correct that RTLD_GLOBAL flag is in some kind of obsolete in 
musl because calling
     dlopen("$libdir/myapp/", RTLD_NOW | RTLD_GLOBAL);
     dlopen("$libdir2/myapp2/", RTLD_LAZY);

    does not allow to find library $libdir/myapp/ 
which it is depend on?

   What is the suggested way in musl to load $libdir/myapp/ 
from a custom directory so can find it?


> Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.