From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: [RFC] EINTR and PC loser-ing library design
Date: Mon, 08 Dec 2014 15:29:53 +0100 [thread overview]
Message-ID: <5485B5E1.90602@skarnet.org> (raw)
In-Reply-To: <20141208141039.GA4574@brightrain.aerifal.cx>
On 08/12/2014 15:10, Rich Felker wrote:
> I don't see what problem you're trying to solve. EINTR does not happen
> unless you intentionally request it by setting up an interrupting
> signal handler, using sigaction() with the SA_RESTART flag clear.
What about SIGSTOP, and its cousins SIGTSTP, SIGTTIN and SIGTTOU ?
Even when you don't request anything, you can receive them. They
stop the process, they don't kill it. What happens when the process
resumes, if it was interrupted in the middle of an interruptible
system call ?
> Retry-on-EINTR loops are generally misguided unless they're in code
> that's intended to be using in programs which use interrupting signal
> handlers, but which need to reliably complete an operation even if
> interrupted.
And that happens all the time in asynchronous event loops where you
handle signals with a self-pipe. ;)
--
Laurent
next prev parent reply other threads:[~2014-12-08 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <esmoarexomn.wl-danny.milo+a@gmail.com>
2014-12-08 14:04 ` dannym
2014-12-08 14:10 ` Rich Felker
2014-12-08 14:29 ` Laurent Bercot [this message]
2014-12-08 14:32 ` Rich Felker
2014-12-08 14:45 ` Laurent Bercot
2014-12-08 15:00 ` Rich Felker
2014-12-08 15:09 ` Rich Felker
2014-12-08 15:18 ` dannym
2014-12-08 15:28 ` Rich Felker
2014-12-08 15:49 ` Laurent Bercot
2014-12-08 16:00 ` 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=5485B5E1.90602@skarnet.org \
--to=ska-dietlibc@skarnet.org \
--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).