public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alfonso Alfonso Peterssen <alfonso.peterssen@oracle.com>
To: "Florian Weimer" <fweimer@redhat.com>,
	"Vivek Das Mohapatra" <vivek@collabora.com>
Cc: "Vivek Das Mohapatra via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [External] : Re: [RFC][PATCH v11 0/7] Implementation of RTLD_SHARED for dlmopen
Date: Wed, 16 Jun 2021 13:08:07 +0000	[thread overview]
Message-ID: <BYAPR10MB2792C6084732825167AFD219860F9@BYAPR10MB2792.namprd10.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2106092349410.6900@noise.cbg.collabora.co.uk>

I'm testing these patches for our use case in GraalVM. We use dlmopen to load several isolated JVMs within the same process.

With the patches I'm hitting the following error:
Inconsistency detected by ld.so: dl-version.c: 205: _dl_check_map_versions: Assert
ion `needed != NULL' failed!

Here's the tail of the LD_DEBUG=all log:
   222389:       trying file=./nptl/tls/x86_64/libpthread.so.0
   222389:       trying file=./nptl/tls/libpthread.so.0
   222389:       trying file=./nptl/x86_64/x86_64/libpthread.so.0
   222389:       trying file=./nptl/x86_64/libpthread.so.0
   222389:       trying file=./nptl/x86_64/libpthread.so.0
   222389:       trying file=./nptl/libpthread.so.0
   222389:
   222389:     checking for version `GLIBC_2.2.5' in file ./dlfcn/libdl.so.2 [0]
required by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAALVM_E
SPRESSO_JVM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so [1]
   222389:     checking for version `GLIBC_2.2.5' in file ./nptl/libpthread.so.0
[0] required by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAAL
VM_ESPRESSO_JVM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so
[1]
   222389:     checking for version `GLIBC_2.3' in file ./libc.so.6 [0] required
by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAALVM_ESPRESSO_J
VM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so [1]
   222389:     checking for version `GLIBC_2.3.2' in file ./libc.so.6 [0] require
d by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAALVM_ESPRESSO
_JVM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so [1]
   222389:     checking for version `GLIBC_2.4' in file ./libc.so.6 [0] required
by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAALVM_ESPRESSO_J
VM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so [1]
   222389:     checking for version `GLIBC_2.2.5' in file ./libc.so.6 [0] require
d by file /home/mukel/Desktop/graal/graal/sdk/mxbuild/linux-amd64/GRAALVM_ESPRESSO
_JVM_EE_JAVA11/graalvm-espresso-jvm-ee-java11-21.2.0-dev/lib/libnio.so [1]
Inconsistency detected by ld.so: dl-version.c: 205: _dl_check_map_versions: Assert
ion `needed != NULL' failed!


We use dlmopen a lot, but never seen this error before, hopefully you can pinpoint the issue. The program in question runs fine without the patches.
I'm running with ./testrun.sh .
I can provide a reproducer, but the setup is quite cumbersome. I can also test any further patches locally if needed.
We've been following this feature for a long time (with great excitement) and just wanted to make sure it works (or that at least doesn't break us) before it's merged.

Best,
Alfonso

________________________________
From: Libc-alpha <libc-alpha-bounces+alfonso.peterssen=oracle.com@sourceware.org> on behalf of Vivek Das Mohapatra via Libc-alpha <libc-alpha@sourceware.org>
Sent: Thursday, June 10, 2021 12:50 AM
To: Florian Weimer <fweimer@redhat.com>
Cc: Vivek Das Mohapatra via Libc-alpha <libc-alpha@sourceware.org>
Subject: [External] : Re: [RFC][PATCH v11 0/7] Implementation of RTLD_SHARED for dlmopen

On Wed, 9 Jun 2021, Florian Weimer wrote:

>>  - libpthread still has the new section applied as I'm not 100% sure it doesn't
>>    still need this treatment. I would like to investigate further before
>
> libpthread does not need this anymore.  We can safely load it as many
> times as we want.

Ok, thanks. I'll update the patch series.

  reply	other threads:[~2021-06-16 13:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 17:16 Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 1/7] Define a new dynamic section tag - DT_GNU_FLAGS_1 (bug 22745) Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 2/7] Abstract loaded-DSO search code into a helper function Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 3/7] Use the new DSO finder " Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 4/7] Add DT_GNU_FLAGS_1/DF_GNU_1_UNIQUE to glibc DSOs (bug 22745) Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 5/7] Implement dlmopen RTLD_SHARED flag " Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 6/7] Add dlmopen / RTLD_SHARED tests Vivek Das Mohapatra
2021-06-09 17:16 ` [RFC][PATCH v11 7/7] Restore separate libc loading for the TLS/namespace storage test Vivek Das Mohapatra
2021-06-09 18:29 ` [RFC][PATCH v11 0/7] Implementation of RTLD_SHARED for dlmopen Florian Weimer
2021-06-09 22:50   ` Vivek Das Mohapatra
2021-06-16 13:08     ` Alfonso Alfonso Peterssen [this message]
2021-06-20 23:18       ` [External] : " Vivek Das Mohapatra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR10MB2792C6084732825167AFD219860F9@BYAPR10MB2792.namprd10.prod.outlook.com \
    --to=alfonso.peterssen@oracle.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=vivek@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).