public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: enh <enh@google.com>
Cc: "Fangrui Song" <maskray@google.com>,
	"Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>,
	"Szabolcs Nagy" <szabolcs.nagy@arm.com>,
	"Cristian Rodríguez" <cristian@rodriguez.im>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	libc-alpha@sourceware.org, "Vitaly Buka" <vitalybuka@google.com>,
	"Fangrui Song" <i@maskray.me>,
	"Evgenii Stepanov" <eugenis@google.com>,
	"Kostya Serebryany" <kcc@google.com>,
	"Dmitry Vyukov" <dvyukov@google.com>
Subject: Re: [PATCH] aarch64: Remove ld.so __tls_get_addr plt usage
Date: Mon, 15 Apr 2024 13:41:29 +0200	[thread overview]
Message-ID: <87ttk2n992.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAJgzZoq=OSDVabOghMu_djquU19u17_1FAqLcGzA5xCamjF4qw@mail.gmail.com> (enh@google.com's message of "Wed, 10 Apr 2024 08:46:57 -0700")

> bionic implemented
> https://sourceware.org/glibc/wiki/ThreadPropertiesAPI in
> https://android.googlesource.com/platform/bionic/+/refs/heads/main/libc/include/sys/thread_properties.h
> but tbh i'm not sure that the sanitizer folks moved over to the new
> api?

I think I wrote about this before: The APIs are underspecified.  I think
we want to be able to change the boundaries of static TLS eventually
(allocating more backing storage before the start or the end, using
address space that previously was only reserved with PROT_NONE).

Maybe I should put it into the wiki page.

> (i don't think we could just use malloc() because jemalloc -- which we
> still haven't fully removed for very low-end users in favor of scudo
> -- was itself using TLS thread locals? scudo has its own reserved
> constant slot in bionic, so that should be fine, i think, but we're
> not there yet.)

Yes, that's the TCB bootstrap problem I mentioned.  It's only relevant
to the initial thread.  There is no functional requirement to allocate
TCBs directly on the thread they are used for.  So once we solve the TCB
issue for the main thread (and have a mode that uses malloc otherwise),
I think we are done.

Thanks,
Florian


  reply	other threads:[~2024-04-15 11:41 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
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 [this message]
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=87ttk2n992.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=cristian@rodriguez.im \
    --cc=dvyukov@google.com \
    --cc=enh@google.com \
    --cc=eugenis@google.com \
    --cc=hjl.tools@gmail.com \
    --cc=i@maskray.me \
    --cc=kcc@google.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maskray@google.com \
    --cc=szabolcs.nagy@arm.com \
    --cc=vitalybuka@google.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).