musl - Re: Incorrect thread TID caching

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <51614DF7-9976-48D3-92F2-B927FCE18663@gmail.com>
Date: Wed, 3 Feb 2021 23:22:18 -0500
From: Dominic Chen <d.c.ddcc@...il.com>
To: Carlos O'Donell <carlos@...hat.com>
Cc: musl@...ts.openwall.com,
 Rich Felker <dalias@...c.org>,
 fweimer@...hat.com
Subject: Re: Incorrect thread TID caching


> On Feb 3, 2021, at 10:28 PM, Carlos O'Donell <carlos@...hat.com> wrote:
> 
> As Rich said for musl, this is not ABI for glibc either.
> 
> I'm not sure why you need to reset the TID cache. In glibc we have
> containerized tests and we do not need to change internals of the 
> runtime e.g. unshare (CLONE_NEWUSER, CLONE_NEWPID, CLONE_NEWNS);
> (see glibc/support/test-container.c).


Thanks for the advice; sounds like I should just modify my local musl to call gettid directly in raise().

As for Chrome, I’m not very familiar with the codebase, but it looks like that code landed back in 2016, as a workaround before the PID/TID cache changes in glibc.

Dominic

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.