From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Szabolcs Nagy" <szabolcs.nagy@arm.com>,
"Cristian Rodríguez" <cristian@rodriguez.im>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Florian Weimer" <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] aarch64: Remove ld.so __tls_get_addr plt usage
Date: Mon, 8 Apr 2024 13:57:02 -0300 [thread overview]
Message-ID: <e3b41fd9-ae79-4507-991e-d9b73e0edf68@linaro.org> (raw)
In-Reply-To: <ZhOcPS5wcrl4arF0@arm.com>
On 08/04/24 04:26, Szabolcs Nagy wrote:
> The 04/07/2024 16:29, Cristian Rodríguez wrote:
>> On Fri, Apr 5, 2024 at 11:59 AM Szabolcs Nagy <szabolcs.nagy@arm.com> wrote:
>>>
>>> The 04/05/2024 09:35, Adhemerval Zanella wrote:
>>>> Use the hidden alias instead.
>>>>
>>>> Checked on aarch64-linux-gnu.
>>>
>>> does this change behaviour in case __tls_get_addr is interposed?
>>
>> Wut ? is that really supported.. I mean.. isn't that symbol prefix
>> reserved for the implementation and any assumption about it is either
>> ID or UB?
>
> a behaviour can change even if it's not supported.
> i did not try to imply that it should be supported.
>
> i know sanitizers interpose __tls_get_addr, because
> https://sourceware.org/bugzilla/show_bug.cgi?id=16291
> i don't know if that hack works at all now for tlsdesc
> (where the ld.so calls __tls_get_addr, not user code)
>
> my question was if we investigated this issue since it
> is useful to document then in the commit msg (or news
> entry if this affects users)
This change 'breaks' the sanitizer trick to get the dynamic TLS, with
this patch I now see:
MemorySanitizer-AARCH64 :: dtls_test.c
SanitizerCommon-asan-aarch64-Linux :: Linux/resize_tls_dynamic.cpp
SanitizerCommon-msan-aarch64-Linux :: Linux/resize_tls_dynamic.cpp
SanitizerCommon-tsan-aarch64-Linux :: Linux/resize_tls_dynamic.cpp
And it does not fail on x86 only because it uses -mtls=gnu as default
(the same tests fail on x86 with -mtls=gnu2).
Now that GCC and distributions are aiming to use GNU2/DESC as the
default TLS, this hack will also break on x86. So the question is
whether we revert 050f7298e1ecc39887c329037575ccd972071255 and
document that __tls_get_addr should be interposable, or move with this
change and try to come up with a possible solution for BZ#16291.
I bringing this because we will have another two ABIs with tlsdesc
support (loongarch and riscv).
next prev parent reply other threads:[~2024-04-08 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:35 Adhemerval Zanella
2024-04-05 14:58 ` Szabolcs Nagy
2024-04-05 16:29 ` Adhemerval Zanella Netto
2024-04-06 17:40 ` Szabolcs Nagy
2024-04-08 8:04 ` Florian Weimer
2024-04-07 20:29 ` Cristian Rodríguez
2024-04-08 7:26 ` Szabolcs Nagy
2024-04-08 16:57 ` Adhemerval Zanella Netto [this message]
2024-04-09 8:30 ` Szabolcs Nagy
2024-04-09 14:03 ` Adhemerval Zanella Netto
2024-04-09 14:05 ` H.J. Lu
2024-04-09 14:11 ` Palmer Dabbelt
2024-04-09 14:46 ` H.J. Lu
2024-04-09 17:50 ` Fangrui Song
2024-04-10 7:29 ` Szabolcs Nagy
2024-04-10 8:23 ` Florian Weimer
2024-04-10 15:46 ` enh
2024-04-15 11:41 ` Florian Weimer
2024-04-15 20:22 ` Adhemerval Zanella Netto
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=e3b41fd9-ae79-4507-991e-d9b73e0edf68@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=cristian@rodriguez.im \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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).