This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: is there plan to support 'linker namespace' in glib?
- From: Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>
- To: zhuao <zhuao at ustc dot edu>, libc-alpha <libc-alpha at sourceware dot org>
- Cc: nd <nd at arm dot com>
- Date: Mon, 11 Mar 2019 12:31:08 +0000
- Subject: Re: is there plan to support 'linker namespace' in glib?
- References: <AHcAmAAJBzshW53NResIkqqz.1.1552302786642.Hmail.zhuao@ustc.edu>
On 11/03/2019 11:13, zhuao wrote:
> I notice that android bionic support 'linker namespace': https://source.android.com/devices/architecture/vndk/linker-namespace
> it provides additional isolation among software components.
> it may also benefit some usage:
> - isolation prebuilt binaries with different toolchain (versioned glibc)
> - it may also give us opportunity to use android binary (HAL) with glibc, by isolating glib and bionic world in different namespace
>
>
> do you think the above approach is possible?
> if yes, is it possible to add such feature to glibc?
glibc supports dlmopen
but i think such isolation does not work reliably
for the libc itself (or anything that tries to
manage application global state) if you need multiple
instances of that module (e.g. different versions of
the libc or a different libc implementations) in the
same process.