public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Remove dead l_need_tls_init static-TLS init path
Date: Wed, 10 Jun 2026 09:33:33 +0200	[thread overview]
Message-ID: <lhuecievohe.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b6191ee1-a380-46d8-aab9-8dab2cdd4c7e@linaro.org> (Adhemerval Zanella Netto's message of "Tue, 9 Jun 2026 13:04:06 -0300")

* Adhemerval Zanella Netto:

> On 09/06/26 11:13, Florian Weimer wrote:
>> * Adhemerval Zanella:
>> 
>>> @@ -671,16 +641,18 @@ dl_open_worker_begin (void *a)
>>>    if (mode & RTLD_GLOBAL)
>>>      add_to_global_resize (new);
>>>  
>>> -  /* Install the new modules in the DTV slotinfo and initialise their
>>> -     static TLS *before* relocation, so an IFUNC resolver firing during
>>> -     the relocation loop below can reach its DSO's __thread storage via
>>> -     __tls_get_addr / TLSDESC.  Without this, the resolver's TLS access
>>> -     for a just-loaded module would index into an unallocated DTV slot
>>> -     and crash.  If relocation later fails, the subsequent _dl_close_worker
>>> -     cleans up these slotinfo entries via remove_slotinfo.  */
>>> +  /* Register the new modules in the DTV slotinfo and bump the TLS
>>> +     generation counter *before* relocation, so an IFUNC resolver firing
>>> +     during the relocation loop below can reach its DSO's __thread storage
>>> +     via __tls_get_addr / TLSDESC.  Without this, the new module is not yet
>>> +     in GL(dl_tls_dtv_slotinfo_list), so the resolver's dynamic-TLS lookup
>>> +     fails to find it and faults.  The static-TLS image itself is copied
>>> +     lazily on first access; for the initial-exec model the static-TLS
>>> +     offset is reserved inline during relocation (see
>>> +     _dl_try_allocate_static_tls), not here.  If relocation later fails,
>>> +     the subsequent _dl_close_worker cleans up these slotinfo entries via
>>> +     remove_slotinfo.  */
>>>    if (any_tls)
>>> -    /* FIXME: This calls _dl_update_slotinfo, which aborts the process
>>> -       on memory allocation failure.  See bug 16134.  */
>>>      update_tls_slotinfo (new);
>> 
>> Is the FIXME truly gone?
> No, BZ 16134 is not fixed, only relocated. That lazy path still aborts:
>   
>   __tls_get_addr -> _dl_update_slotinfo -> _dl_resize_dtv -> oom
>
> Per:
>
> elf/dt-tls.c
>
>  921                   /* Resizing the dtv aborts on failure: bug 16134.  */
>  922                   dtv = _dl_resize_dtv (dtv, max_modid, THREAD_SELF);

Sorry, then why remove the comment?

Thanks,
Florian


  reply	other threads:[~2026-06-10  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 13:25 Adhemerval Zanella
2026-06-09 14:13 ` Florian Weimer
2026-06-09 16:04   ` Adhemerval Zanella Netto
2026-06-10  7:33     ` Florian Weimer [this message]
2026-06-10 11:46       ` Adhemerval Zanella Netto
2026-06-23 12:23 ` Adhemerval Zanella Netto
2026-08-03 13:01 ` Florian Weimer
2026-08-03 14:23   ` 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=lhuecievohe.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).