From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3] elf: Fix DTV gap reuse logic (BZ #27135)
Date: Wed, 14 Jul 2021 15:11:53 -0300 [thread overview]
Message-ID: <bc71f5d4-cd1f-aa21-91d6-5c71153043a6@linaro.org> (raw)
In-Reply-To: <76323d51-f54d-29c1-1a72-3b439c521f44@redhat.com>
On 14/07/2021 13:57, Carlos O'Donell wrote:
> On 7/14/21 9:52 AM, Adhemerval Zanella wrote:
>>
>>
>> On 09/07/2021 12:05, Szabolcs Nagy wrote:
>>> The 07/09/2021 10:50, Adhemerval Zanella wrote:
>>>> Changes from previous version:
>>>>
>>>> - Fix commit message and add a line about the bug fixes.
>>>> - Use atomic operation while setting the slotinfo.
>>>> - Use test_verbose on tst-tls20.c.
>>>>
>>>> ---
>>>>
>>>> This is updated version of the 572bd547d57a (reverted by 40ebfd016ad2)
>>>> that fixes the _dl_next_tls_modid issues.
>>>>
>>>> This issue with 572bd547d57a patch is the DTV entry will be only
>>>> update on dl_open_worker() with the update_tls_slotinfo() call after
>>>> all dependencies are being processed by _dl_map_object_deps(). However
>>>> _dl_map_object_deps() itself might call _dl_next_tls_modid(), and since
>>>> the _dl_tls_dtv_slotinfo_list::map is not yet set the entry will be
>>>> wrongly reused.
>>>>
>>>> This patch fixes by renaming the _dl_next_tls_modid() function to
>>>> _dl_assign_tls_modid() and by passing the link_map so it can set
>>>> the slotinfo value so a so subsequente _dl_next_tls_modid() call will
>>>> see the entry as allocated.
>>>
>>> this paragraph still has 'so a so subsequente'
>>> and i would add the bug number into the first sentence.
>>
>> Fixed.
>>
>>>
>>>>
>>>> The intermediary value is cleared up on remove_slotinfo() for the case
>>>> a library fails to load with RTLD_NOW.
>>>>
>>>> This patch fixes BZ #27135.
>>>>
>>>> Checked on x86_64-linux-gnu.
>>>
>>> the patch looks ok to me, with the commit message
>>> and the comment issue below fixed.
>>>
>>> Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
>>
>> Carlos, is it for push?
>
> It's a non-ABI bug fix, so we can push it. Thanks for asking.
>
And it is in, let's hope it does not brake anything again ;)
next prev parent reply other threads:[~2021-07-14 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 13:50 [PATCH v3] elf: Fix DTV gap reuse logic (BZ #27135) Adhemerval Zanella via Libc-alpha
2021-07-09 15:05 ` Szabolcs Nagy via Libc-alpha
2021-07-14 13:52 ` Adhemerval Zanella via Libc-alpha
2021-07-14 16:57 ` Carlos O'Donell via Libc-alpha
2021-07-14 18:11 ` Adhemerval Zanella via Libc-alpha [this message]
2021-07-15 13:36 ` Stefan Liebler via Libc-alpha
2021-07-15 13:40 ` Adhemerval Zanella via Libc-alpha
2021-07-15 13:51 ` Adhemerval Zanella via Libc-alpha
2021-07-15 15:03 ` Stefan Liebler via Libc-alpha
2021-07-09 20:05 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc71f5d4-cd1f-aa21-91d6-5c71153043a6@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--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).