Update list of async-sygnal-safe functions for POSIX.1-2008.

This commit is contained in:
Michael Kerrisk 2008-08-21 06:38:19 +00:00
parent 2773008f52
commit a0f7c7d8ba
1 changed files with 29 additions and 2 deletions

View File

@ -40,7 +40,7 @@
.\" Added section on system call restarting (SA_RESTART)
.\" Added section on stop/cont signals interrupting syscalls.
.\"
.TH SIGNAL 7 2008-07-07 "Linux" "Linux Programmer's Manual"
.TH SIGNAL 7 2008-08-21 "Linux" "Linux Programmer's Manual"
.SH NAME
signal \- list of available signals
.SH DESCRIPTION
@ -356,7 +356,6 @@ calls an unsafe function, then the behavior of the program is undefined.
POSIX.1-2004 (also known as POSIX.1-2001 Technical Corrigendum 2)
requires an implementation to guarantee that the following
functions can be safely called inside a signal handler:
.\" FIXME . SUSv4 adds functions to this list, and removes a few.
.in +4
.nf
@ -480,6 +479,34 @@ waitpid()
write()
.fi
.in
.PP
POSIX.1-2008 removes fpathconf(), pathconf(), and sysconf()
from the above list, and adds the following functions:
.PP
.in +4n
.nf
execl()
execv()
faccessat()
fchmodat()
fchownat()
fexecve()
fstatat()
futimens()
linkat()
mkdirat()
mkfifoat()
mknod()
mknodat()
openat()
readlinkat()
renameat()
symlinkat()
unlinkat()
utimensat()
utimes()
.fi
.in
.SS Interruption of System Calls and Library Functions by Signal Handlers
If a signal handler is invoked while a system call or library
function call is blocked, then either: