From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>, libc-alpha@sourceware.org
Subject: Re: elf: Fix slow tls access after dlopen [BZ #19924]
Date: Tue, 30 May 2023 08:42:24 -0300 [thread overview]
Message-ID: <acd9d6ec-dd7e-71ca-5d93-e65c4b911951@linaro.org> (raw)
In-Reply-To: <p9u0leh66ziw.fsf@coriandre.loria.fr>
On 30/05/23 04:37, Paul Zimmermann via Libc-alpha wrote:
> a gentle ping for this patch from January 6 which is stilled marked "New":
>
> https://patchwork.sourceware.org/project/glibc/patch/20230106185250.2936935-1-szabolcs.nagy@arm.com/
>
> As I understand, the goal was to have it in the next release.
>
> Paul
Hi Paul, I will try to take a look at this patch. This does seems important to
a handful of projects and it would be good to have it fixed.
next prev parent reply other threads:[~2023-05-30 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 7:37 Paul Zimmermann
2023-05-30 11:42 ` Adhemerval Zanella Netto [this message]
2023-05-30 12:13 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2023-07-04 7:50 Paul Zimmermann
2023-02-21 11:56 Paul Zimmermann
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=acd9d6ec-dd7e-71ca-5d93-e65c4b911951@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Paul.Zimmermann@inria.fr \
--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).