[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <lhuecejhump.fsf@oldenburg.str.redhat.com>
Date: Thu, 24 Sep 2026 11:21:50 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Rich Felker <dalias@...c.org>
Cc: Trevor Gross <tg@...vorgross.com>, musl@...ts.openwall.com,
linux-man@...r.kernel.org, libc-alpha@...rceware.org
Subject: Re: Re: async-signal-safety of chroot
* Rich Felker:
> musl makes clone roughly as safe as fork (see commit fa4a8abd06a4),
> and disallows flags that are not compatible with executing any part of
> libc in the child, but afaik glibc still has an anything-goes
> approach.
Yes, there is no filtering in glibc, and no update of the (shared) TCB.
Several web browsers longjmp out of the clone callback and patch the TCB
with the new TID, so that mutexes work as expected.
Thanks,
Florian
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
