[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d28fcf7-b869-175d-c2b7-9c61ef1d40cd@redhat.com>
Date: Tue, 3 Jul 2018 17:08:21 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: arc4random/csprng
On 07/03/2018 04:47 PM, Rich Felker wrote:
>> The main lock (for non-current kernels) is needed for the fork
>> detection counters. Fork detection is required for compatibility
>> with applications which call clone/fork system calls directly, so
>
> How do you consider this supported usage at all? The tid in the TCB
> will be invalid after such a call, and other things may be broken too.
Right, robust mutexes are quite broken by this.
But it's still quite common to do things with direct system calls,
particularly for setting up containers.
I have not yet found a case which I couldn't solve with plain fork (with
handlers) and unshare, but that's not what everyone does unfortunately.
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.
