Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 08 Dec 2014 15:45:33 +0100
From: Laurent Bercot <ska-dietlibc@...rnet.org>
To: musl@...ts.openwall.com
Subject: Re: [RFC] EINTR and PC loser-ing library design

On 08/12/2014 15:32, Rich Felker wrote:

> The system call restarts (or, formally, it's as if it were never
> interrupted; EINTR only applies to signal _handlers_).

  Could you please provide a pointer to the specification that
guarantees this ? I've never been able to find a normative text that
ensures you will never get EINTR unless you explicitly install a
signal handler without SA_RESTART.


>>   And that happens all the time in asynchronous event loops where you
>> handle signals with a self-pipe. ;)
>
> Only if you have installed interrupting signal handlers.

  Which basically means any signal except SIGCHLD.

-- 
  Laurent

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.