runtime, syscall: SA_RESTART does not affect all system calls

[PieterD]

http://man7.org/linux/man-pages/man7/signal.7.html

The following interfaces are never restarted after being interrupted by a signal handler, regardless of the use of SA_RESTART; they always fail with the error EINTR when interrupted by a signal handler:

What follows is a list of system calls including "File descriptor multiplexing interfaces" and "System V IPC interfaces" (and inotify before Linux 3.8, which is how I found out in the first place: see #9782).

The standard library should be checked for use of these system calls and, where required, keep EINTR in mind.

[davecheney]

This is why we can't have nice things.
On 6 Feb 2015 10:12, "Pieter Droogendijk" notifications@github.com wrote:

http://man7.org/linux/man-pages/man7/signal.7.html

The following interfaces are never restarted after being interrupted by a
signal handler, regardless of the use of SA_RESTART; they always fail with
the error EINTR when interrupted by a signal handler:

What follows is a list of system calls including "File descriptor
multiplexing interfaces" and "System V IPC interfaces" (and inotify before
Linux 3.8, which is how I found out in the first place: see #9782
#9782).

The standard library should be checked for use of these system calls and,
where required, keep EINTR in mind.

—
Reply to this email directly or view it on GitHub
#9785.

[bradfitz]

/cc @ianlancetaylor for thoughts.

[ianlancetaylor]

My only thought is that the last time I looked at this they were all handled correctly. I have no objection to somebody else checking.

[rsc]

Unless you know of a specific problem, I don't see any work here.