From fb16ec35858fcb6dcb618dd76cc4217db574be81 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Wed, 9 Nov 2016 13:42:37 +0100 Subject: [PATCH] signal-safety.7: Note glibc deviations from POSIX requirements See https://bugzilla.kernel.org/show_bug.cgi?id=25292 Reported-by: KASAKI Motohiro Signed-off-by: Michael Kerrisk --- man7/signal-safety.7 | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/man7/signal-safety.7 b/man7/signal-safety.7 index 0ca44b122..42c639478 100644 --- a/man7/signal-safety.7 +++ b/man7/signal-safety.7 @@ -301,6 +301,27 @@ or .BR siglongjmp (3) and the program subsequently calls an unsafe function, then the behavior of the program is undefined. +.\" +.SS Deviations in the GNU C library +The following known deviations from the standard occur in +the GNU C library: +.IP * 3 +Before glibc 2.24, +.BR execl (3) +and +.BR execle (3) +employed +.BR realloc (3) +internally and were consequently not async-signal-safe. +.\" https://sourceware.org/bugzilla/show_bug.cgi?id=19534 +This was fixed in glibc 2.24. +.IP * +.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=13172 +The glibc implementation of +.BR aio_suspend (3) +is not async-signal-safe because it uses +.BR pthread_mutex_lock (3) +internally. .SH SEE ALSO .BR sigaction (2), .BR signal (7),