From: Florian Weimer <fweimer@redhat.com>
To: "Vivek Das Mohapatra via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [RFC][PATCH v11 0/7] Implementation of RTLD_SHARED for dlmopen
Date: Wed, 09 Jun 2021 20:29:12 +0200 [thread overview]
Message-ID: <87zgvy3n9j.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210609171618.20674-1-vivek@collabora.com> ("Vivek =?utf-8?Q?Das=C2=A0Mohapatra?= via Libc-alpha"'s message of "Wed, 9 Jun 2021 18:16:11 +0100")
* Vivek Das Mohapatra via Libc-alpha:
> - 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
> removing the new section from libpthread.
libpthread does not need this anymore. We can safely load it as many
times as we want.
librt still needs it because it's not empty and has global state (for
handling the thread notifications).
Thanks,
Florian
next prev parent reply other threads:[~2021-06-09 18:29 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 ` Florian Weimer [this message]
2021-06-09 22:50 ` [RFC][PATCH v11 0/7] Implementation of RTLD_SHARED for dlmopen Vivek Das Mohapatra
2021-06-16 13:08 ` [External] : " Alfonso Alfonso Peterssen
2021-06-20 23:18 ` 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=87zgvy3n9j.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).