[MTASCsft PATCH WIP5 27/33] MT-, AS- and AC-safety docs: manual/socket.texi

[Alexandre Oliva <aoliva at redhat dot com>]

for ChangeLog

	* manual/socket.texi: Document MTASC-safety properties.
---
 manual/socket.texi |    5 +++++
 1 file changed, 5 insertions(+)

diff --git a/manual/socket.texi b/manual/socket.texi
index 4c7e623..e428615 100644
--- a/manual/socket.texi
+++ b/manual/socket.texi
@@ -1771,6 +1771,7 @@ declared in @file{sys/socket.h}.
 @comment sys/socket.h
 @comment BSD
 @deftypefun int socket (int @var{namespace}, int @var{style}, int @var{protocol})
+@safety{@mtsafe{}@assafe{}@acsafe{fdleak}}
 This function creates a socket and specifies communication style
 @var{style}, which should be one of the socket styles listed in
 @ref{Communication Styles}.  The @var{namespace} argument specifies
@@ -1977,6 +1978,7 @@ program must do with the @code{connect} function, which is declared in
 @comment sys/socket.h
 @comment BSD
 @deftypefun int connect (int @var{socket}, struct sockaddr *@var{addr}, socklen_t @var{length})
+@safety{@mtsafe{}@assafe{}@acsafe{}}
 The @code{connect} function initiates a connection from the socket
 with file descriptor @var{socket} to the socket whose address is
 specified by the @var{addr} and @var{length} arguments.  (This socket
@@ -2254,6 +2256,7 @@ you get a @code{SIGPIPE} signal for any use of @code{send} or
 @comment sys/socket.h
 @comment BSD
 @deftypefun ssize_t send (int @var{socket}, const void *@var{buffer}, size_t @var{size}, int @var{flags})
+@safety{@mtsafe{}@assafe{}@acsafe{}}
 The @code{send} function is like @code{write}, but with the additional
 flags @var{flags}.  The possible values of @var{flags} are described
 in @ref{Socket Data Options}.
@@ -2731,6 +2734,7 @@ you don't want to specify @var{flags} (@pxref{I/O Primitives}).
 @comment sys/socket.h
 @comment BSD
 @deftypefun ssize_t sendmsg (int @var{socket}, const struct msghdr *@var{message}, int @var{flags})
+@safety{@mtsafe{}@assafe{}@acsafe{}}
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
@@ -2742,6 +2746,7 @@ whatever) are freed even if the thread is cancel.
 @comment sys/socket.h
 @comment BSD
 @deftypefun ssize_t recvmsg (int @var{socket}, struct msghdr *@var{message}, int @var{flags})
+@safety{@mtsafe{}@assafe{}@acsafe{}}
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that