mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Dominic Chen <d.c.ddcc@gmail.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: musl@lists.openwall.com, Rich Felker <dalias@libc.org>,
	fweimer@redhat.com
Subject: Re: [musl] Incorrect thread TID caching
Date: Wed, 3 Feb 2021 23:22:18 -0500	[thread overview]
Message-ID: <51614DF7-9976-48D3-92F2-B927FCE18663@gmail.com> (raw)
In-Reply-To: <634da58e-77d0-bea4-8ebf-f2c1fc933fee@redhat.com>


> On Feb 3, 2021, at 10:28 PM, Carlos O'Donell <carlos@redhat.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

  reply	other threads:[~2021-02-04  4:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  4:04 Dominic Chen
2021-02-03  7:16 ` Florian Weimer
2021-02-03 19:21 ` Rich Felker
2021-02-03 20:21   ` Dominic Chen
2021-02-03 21:01     ` Rich Felker
2021-02-03 22:30       ` Dominic Chen
2021-02-03 22:55         ` Rich Felker
2021-02-15 16:56           ` Rich Felker
2021-02-17 19:49             ` Dominic Chen
2021-02-17 20:11               ` Rich Felker
2021-02-17 21:07                 ` Rich Felker
2021-03-12 21:14                   ` Dominic Chen
2021-02-04  3:28     ` Carlos O'Donell
2021-02-04  4:22       ` Dominic Chen [this message]
2021-02-04 16:15         ` Rich Felker

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=51614DF7-9976-48D3-92F2-B927FCE18663@gmail.com \
    --to=d.c.ddcc@gmail.com \
    --cc=carlos@redhat.com \
    --cc=dalias@libc.org \
    --cc=fweimer@redhat.com \
    --cc=musl@lists.openwall.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).