[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.20.13.1801310111320.604@monopod.intra.ispras.ru>
Date: Wed, 31 Jan 2018 01:20:45 +0300 (MSK)
From: Alexander Monakov <amonakov@...ras.ru>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] faccessat: fix error code on setreXid failure
On Tue, 30 Jan 2018, Rich Felker wrote:
> > We know we are not tracing this child, and stop notifications are only
> > delivered if WUNTRACED is given in flags, aren't they?
>
> I'm not sure what can happen if it's all running under strace -f or
> something. And I'm not sure what the conditions for stop notifications
> are. If it's assured that they can't happen then maybe the loop can be
> removed.
Well, currently musl is just inconsistent, as in other instance(s?)
(most notably in posix_spawn) it makes a single call to waitpid
without retrying even though the same concerns apply.
Alexander
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.
