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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: