Merge branch 'bmk/erts/esock/20190529/expose_select_to_the_caller/OTP-15731' into maint

2 files changed, 354 insertions, 21 deletions

diff --git a/erts/doc/src/socket.xml b/erts/doc/src/socket.xml
index 9b34bf1df1..b4e22e86a8 100644
--- a/erts/doc/src/socket.xml
+++ b/erts/doc/src/socket.xml
@@ -41,6 +41,38 @@
     e.g. <seealso marker="#recv/3"><c>recv/3</c></seealso>, 
     has a timeout argument. </p>
     <note>
+      <p>Some functions allow for an <i>asynchronous</i> call.
+      This is achieved by setting the <c>Timeout</c> argument to
+      <c>nowait</c>. For instance, if calling the
+      <seealso marker="#recv_async"><c>recv/3</c></seealso>
+      function with Timeout set to <c>nowait</c> (<c>recv(Sock, 0, nowait)</c>)
+      when there is actually nothing to read, it will return with
+      <c>{ok, </c>
+      <seealso marker="#type-select_info"><c>SelectInfo</c></seealso><c>}</c>.
+      When data eventually arrives a 'select' message
+      will be sent to the caller: </p>
+      <taglist>
+	<!-- NOTE THAT THE EMPTY TAG IS INTENTIONAL -->
+	<tag></tag>
+	<item><c>{'$socket', socket(), select, select_ref()}</c></item>
+      </taglist>
+      <p>The caller can now make another
+      call to the recv function and now expect data.</p>
+      <p>Note that all other users are <em>locked out</em> until the
+      'current user' has called the function (recv in this case).</p>
+      <p>Another message the user must be prepared for (when making asynchronous
+      calls) is the <c>abort</c> message:</p>
+      <taglist>
+	<!-- NOTE THAT THE EMPTY TAG IS INTENTIONAL -->
+	<tag></tag>
+	<item><c>{'$socket', socket(), abort, Info}</c></item>
+      </taglist>
+      <p>This message indicates
+      that the (asynchronous) operation has been aborted.
+      If, for instance, the socket has been closed (by another process),
+      <c>Info</c> will be <c>{select_ref(), closed}</c>. </p>
+    </note>
+    <note>
       <p>There is currently <em>no</em> support for Windows. </p>
       <p>Support for IPv6 has been implemented but <em>not</em> tested. </p>
       <p>SCTP has only been partly implemented (and not tested). </p>
@@ -65,6 +97,21 @@
       </desc>
     </datatype>
     <datatype>
+      <name name="select_tag"/>
+      <desc>
+	<p>A tag that describes the (select) operation.</p>
+      </desc>
+    </datatype>
+    <datatype>
+      <name name="select_ref"/>
+      <desc>
+	<p>A reference that uniquely identifies the (select) operation.</p>
+      </desc>
+    </datatype>
+    <datatype>
+      <name name="select_info"/>
+    </datatype>
+    <datatype>
       <name name="ip4_address"/>
     </datatype>
     <datatype>
@@ -257,7 +304,7 @@
   <funcs>
     <func>
       <name name="accept" arity="1" since="OTP 22.0"/>
-      <name name="accept" arity="2" since="OTP 22.0"/>
+      <name name="accept" arity="2" clause_i="2" since="OTP 22.0"/>
       <fsummary>Accept a connection on a socket.</fsummary>
       <desc>
         <p>Accept a connection on a socket.</p>
@@ -269,6 +316,26 @@
     </func>
 
     <func>
+      <name name="accept" arity="2" clause_i="1" anchor="accept_async" since="OTP @OTP-15731@"/>
+      <fsummary>Accept a connection on a socket.</fsummary>
+      <desc>
+        <p>Accept a connection on a socket.</p>
+
+	<p>This call is used with connection-based socket types
+	(<c>stream</c> or <c>seqpacket</c>). It extracs the first pending
+	connection request for the listen socket and returns the (newly)
+	connected socket.</p>
+
+	<p>In the case when there is no connections waiting, the function 
+	will return with the <c>SelectInfo</c>. The caller can then await a 
+	select message, <c>{'$socket', Socket, select, Info}</c> (where
+	<c>Info</c> is the <c>select_ref()</c> from the <c>SelectInfo</c>),
+	when a client connects (a subsequent call to accept will then return 
+	the socket). </p>
+      </desc>
+    </func>
+
+    <func>
       <name name="bind" arity="2" since="OTP 22.0"/>
       <fsummary>Bind a name to a socket.</fsummary>
       <desc>
@@ -282,6 +349,18 @@
     </func>
 
     <func>
+      <name name="cancel" arity="2" since="OTP @OTP-15731@"/>
+      <fsummary>Cancel an asynchronous request.</fsummary>
+      <desc>
+	<p>Cancel an asynchronous request.</p>
+
+	<p>Call this function in order to cancel a previous
+	asynchronous call to, e.g.
+	<seealso marker="#recv/3"><c>recv/3</c></seealso>. </p>
+      </desc>
+    </func>
+
+    <func>
       <name name="close" arity="1" since="OTP 22.0"/>
       <fsummary>Close a socket.</fsummary>
       <desc>
@@ -302,7 +381,7 @@
 
     <func>
       <name name="connect" arity="2" since="OTP 22.0"/>
-      <name name="connect" arity="3" since="OTP 22.0"/>
+      <name name="connect" arity="3" clause_i="2" since="OTP 22.0"/>
       <fsummary>Initiate a connection on a socket.</fsummary>
       <desc>
         <p>This function connects the socket to the address
@@ -311,6 +390,24 @@
     </func>
 
     <func>
+      <name name="connect" arity="3" clause_i="1" anchor="connect_async" since="OTP @OTP-15731@"/>
+      <fsummary>Initiate a connection on a socket.</fsummary>
+      <desc>
+        <p>This function connects the socket to the address
+	specied by the <c>SockAddr</c> argument.</p>
+
+ 	<p>In the case when its not possible to immediately establish a
+	connection, the function will return with the
+	<seealso marker="#type-select_info"><c>SelectInfo</c></seealso>.
+	The caller can then await a 
+	select message, <c>{'$socket', Socket, select, Info}</c> (where
+	<c>Info</c> is the <c>select_ref()</c> from the <c>SelectInfo</c>,
+	a subsequent call to connect will then 
+	establish the connection). </p>
+     </desc>
+    </func>
+
+    <func>
       <name name="getopt" arity="3" clause_i="1" since="OTP 22.0"/>
       <name name="getopt" arity="3" clause_i="2" since="OTP 22.0"/>
       <name name="getopt" arity="3" clause_i="3" since="OTP 22.0"/>
@@ -406,8 +503,8 @@
       <name name="recv" arity="1" since="OTP 22.0"/>
       <name name="recv" arity="2" since="OTP 22.0"/>
       <name name="recv" arity="3" clause_i="1" since="OTP 22.0"/>
-      <name name="recv" arity="3" clause_i="2" since="OTP 22.0"/>
-      <name name="recv" arity="4" since="OTP 22.0"/>
+      <name name="recv" arity="3" clause_i="3" since="OTP 22.0"/>
+      <name name="recv" arity="4" clause_i="2" since="OTP 22.0"/>
       <fsummary>Receive a message from a socket.</fsummary>
       <desc>
         <p>Receive a message from a socket.</p>
@@ -418,36 +515,91 @@
     </func>
 
     <func>
+      <name name="recv" arity="3" clause_i="2" anchor="recv_async" since="OTP @OTP-15731@"/>
+      <name name="recv" arity="4" clause_i="1" since="OTP @OTP-15731@"/>
+      <fsummary>Receive a message from a socket.</fsummary>
+      <desc>
+        <p>Receive a message from a socket.</p>
+
+	<p>There is a special case for the argument <c>Length</c>.
+	If it is set to zero (0), it means "give me everything you 
+	currently have".</p>
+
+	<p>In the case when there is no data waiting, the function 
+	will return with the <c>SelectInfo</c>. The caller can then await a 
+	select message, <c>{'$socket', Socket, select, Info}</c> (where
+	<c>Info</c> is the <c>select_ref()</c> from the <c>SelectInfo</c>),
+	when data has arrived (a subsequent call to recv will then return 
+	the data). </p>
+	<p>Note that if a length (<c>> 0</c>) is specified, and only part
+	of that amount of data is available, the function will return with
+	that data <em>and</em> the <c>SelectInfo</c> (if the caller don't 
+	want to wait for the remaining data, it must immediately call
+	the <seealso marker="#cancel/2"><c>cancel/2</c></seealso> function.)</p>
+      </desc>
+    </func>
+
+    <func>
       <name name="recvfrom" arity="1" since="OTP 22.0"/>
       <name name="recvfrom" arity="2" since="OTP 22.0"/>
-      <name name="recvfrom" arity="3" clause_i="1" since="OTP 22.0"/>
       <name name="recvfrom" arity="3" clause_i="2" since="OTP 22.0"/>
       <name name="recvfrom" arity="3" clause_i="3" since="OTP 22.0"/>
-      <name name="recvfrom" arity="4" since="OTP 22.0"/>
+      <name name="recvfrom" arity="3" clause_i="5" since="OTP 22.0"/>
+      <name name="recvfrom" arity="4" clause_i="2" since="OTP 22.0"/>
       <fsummary>Receive a message from a socket.</fsummary>
       <desc>
         <p>Receive a message from a socket.</p>
         <p>This function reads "messages", which means that regardless of
-	how much we want to read, it returns when we get a message.</p>
+	how much we want to read, it returns when we get a message
+	(if the buffer size is to small, the message will be truncated).</p>
+        <p>The <c>BufSz</c> argument basically defines the size of the
+	receive buffer. By setting the value to zero (0), the configured
+	size (setopt with <c>Level</c> = <c>otp</c> and
+	<c>Key</c> = <c>rcvbuf</c>) is used.</p>
+        <p>It may be impossible to know what (buffer) size is appropriate
+	"in advance", and in those cases it may be convenient to use the
+	(recv) 'peek' flag. When this flag is provided, the message is *not*
+	"consumed" from the underlying buffers, so another recvfrom call
+	is needed, possibly with a then adjusted buffer size.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name name="recvfrom" arity="3" clause_i="1" anchor="recvfrom_async" since="OTP @OTP-15731@"/>
+      <name name="recvfrom" arity="3" clause_i="4" since="OTP @OTP-15731@"/>
+      <name name="recvfrom" arity="4" clause_i="1" since="OTP @OTP-15731@"/>
+      <fsummary>Receive a message from a socket.</fsummary>
+      <desc>
+        <p>Receive a message from a socket.</p>
+        <p>This function reads "messages", which means that regardless of
+	how much we want to read, it returns when we get a message
+	(if the buffer size is to small, the message will be truncated).</p>
         <p>The <c>BufSz</c> argument basically defines the size of the
 	receive buffer. By setting the value to zero (0), the configured
-	size (setopt with <c>Level</c> = <c>otp</c> and <c>Key</c> = <c>rcvbuf</c>)
-	is used.</p>
+	size (setopt with <c>Level</c> = <c>otp</c> and
+	<c>Key</c> = <c>rcvbuf</c>) is used.</p>
         <p>It may be impossible to know what (buffer) size is appropriate
 	"in advance", and in those cases it may be convenient to use the
 	(recv) 'peek' flag. When this flag is provided, the message is *not*
 	"consumed" from the underlying buffers, so another recvfrom call
 	is needed, possibly with a then adjusted buffer size.</p>
+
+	<p>In the case when there is no data waiting, the function 
+	will return with the <c>SelectInfo</c>. The caller can then await a 
+	select message, <c>{'$socket', Socket, select, Info}</c> (where
+	<c>Info</c> is the <c>select_ref()</c> from the <c>SelectInfo</c>),
+	when data has arrived (a subsequent call to recvfrom will then return 
+	the data). </p>
       </desc>
     </func>
 
     <func>
       <name name="recvmsg" arity="1" since="OTP 22.0"/>
       <name name="recvmsg" arity="2" clause_i="1" since="OTP 22.0"/>
-      <name name="recvmsg" arity="2" clause_i="2" since="OTP 22.0"/>
-      <name name="recvmsg" arity="3" clause_i="1" since="OTP 22.0"/>
+      <name name="recvmsg" arity="2" clause_i="3" since="OTP 22.0"/>
       <name name="recvmsg" arity="3" clause_i="2" since="OTP 22.0"/>
-      <name name="recvmsg" arity="5" since="OTP 22.0"/>
+      <name name="recvmsg" arity="3" clause_i="3" since="OTP 22.0"/>
+      <name name="recvmsg" arity="5" clause_i="2" since="OTP 22.0"/>
       <fsummary>Receive a message from a socket.</fsummary>
       <desc>
         <p>Receive a message from a socket.</p>
@@ -461,8 +613,8 @@
 	
         <p>The <c>BufSz</c> argument basically defines the size of the
 	receive buffer. By setting the value to zero (0), the configured
-	size (setopt with <c>Level</c> = <c>otp</c> and <c>Key</c> = <c>rcvbuf</c>)
-	is used.</p>
+	size (setopt with <c>Level</c> = <c>otp</c> and
+	<c>Key</c> = <c>rcvbuf</c>) is used.</p>
 
         <p>The <c>CtrlSz</c> argument basically defines the size of the
 	receive buffer for the control messages.
@@ -478,21 +630,83 @@
     </func>
 
     <func>
+      <name name="recvmsg" arity="2" clause_i="2" anchor="recvmsg_async" since="OTP @OTP-15731@"/>
+      <name name="recvmsg" arity="3" clause_i="1" since="OTP @OTP-15731@"/>
+      <name name="recvmsg" arity="5" clause_i="1" since="OTP @OTP-15731@"/>
+      <fsummary>Receive a message from a socket.</fsummary>
+      <desc>
+        <p>Receive a message from a socket.</p>
+        <p>This function reads "messages", which means that regardless of
+	how much we want to read, it returns when we get a message.</p>
+	<p>The message will be delivered in the form of a <c>msghdr()</c>,
+	which may contain the source address (if socket not connected),
+	a list of <c>cmsghdr_recv()</c> (depends on what socket options have
+	been set and what the protocol and platform supports) and
+	also a set of flags, providing further info about the read. </p>
+	
+        <p>The <c>BufSz</c> argument basically defines the size of the
+	receive buffer. By setting the value to zero (0), the configured
+	size (setopt with <c>Level</c> = <c>otp</c> and
+	<c>Key</c> = <c>rcvbuf</c>) is used.</p>
+
+        <p>The <c>CtrlSz</c> argument basically defines the size of the
+	receive buffer for the control messages.
+	By setting the value to zero (0), the configured size (setopt
+	with <c>Level</c> = <c>otp</c>) is used.</p>
+
+	<p>It may be impossible to know what (buffer) size is appropriate
+	"in advance", and in those cases it may be convenient to use the
+	(recv) 'peek' flag. When this flag is provided, the message is *not*
+	"consumed" from the underlying buffers, so another recvmsg call
+	is needed, possibly with a then adjusted buffer size.</p>
+
+	<p>In the case when there is no data waiting, the function 
+	will return with the <c>SelectInfo</c>. The caller can then await a 
+	select message, <c>{'$socket', Socket, select, Info}</c> (where
+	<c>Info</c> is the <c>select_ref()</c> from the <c>SelectInfo</c>),
+	when data has arrived (a subsequent call to recvmsg will then return 
+	the data). </p>
+      </desc>
+    </func>
+
+    <func>
       <name name="send" arity="2" since="OTP 22.0"/>
       <name name="send" arity="3" clause_i="1" since="OTP 22.0"/>
-      <name name="send" arity="3" clause_i="2" since="OTP 22.0"/>
-      <name name="send" arity="4" since="OTP 22.0"/>
+      <name name="send" arity="3" clause_i="3" since="OTP 22.0"/>
+      <name name="send" arity="4" clause_i="2" since="OTP 22.0"/>
+      <fsummary>Send a message on a socket.</fsummary>
+      <desc>
+        <p>Send a message on a connected socket.</p>
+      </desc>
+    </func>
+
+    <func>
+      <name name="send" arity="3" clause_i="2" anchor="send_async" since="OTP @OTP-15731@"/>
+      <name name="send" arity="4" clause_i="1" since="OTP @OTP-15731@"/>
       <fsummary>Send a message on a socket.</fsummary>
       <desc>
         <p>Send a message on a connected socket.</p>
+
+	<p>In the case when there is no room in the (system-) buffers,
+	the function will return with the <c>SelectInfo</c>. The caller
+	can then await a select message,
+	<c>{'$socket', Socket, select, Info}</c>
+	(where <c>Info</c> is the <c>select_ref()</c> from the
+	<c>SelectInfo</c>), when there is room for more data (a subsequent
+	call to send will then send the data). </p>
+	<p>Note that if not all the data was sent, the function will return
+	with the remaining data <em>and</em> the <c>SelectInfo</c>
+	(if the caller don't 
+	want to wait to be able to send the rest, it should immediately call
+	the <seealso marker="#cancel/2"><c>cancel/2</c></seealso> function.)</p>
       </desc>
     </func>
 
     <func>
       <name name="sendmsg" arity="2" since="OTP 22.0"/>
       <name name="sendmsg" arity="3" clause_i="1" since="OTP 22.0"/>
-      <name name="sendmsg" arity="3" clause_i="2" since="OTP 22.0"/>
-      <name name="sendmsg" arity="4" since="OTP 22.0"/>
+      <name name="sendmsg" arity="3" clause_i="3" since="OTP 22.0"/>
+      <name name="sendmsg" arity="4" clause_i="2" since="OTP 22.0"/>
       <fsummary>Send a message on a socket.</fsummary>
       <desc>
 	<p>Send a message on a socket. The destination, if needed
@@ -513,10 +727,39 @@
     </func>
 
     <func>
+      <name name="sendmsg" arity="3" clause_i="2" anchor="sendmsg_async" since="OTP @OTP-15731@"/>
+      <name name="sendmsg" arity="4" clause_i="1" since="OTP @OTP-15731@"/>
+      <fsummary>Send a message on a socket.</fsummary>
+      <desc>
+	<p>Send a message on a socket. The destination, if needed
+	(socket <em>not</em> connected) is provided in the <c>MsgHdr</c>,
+	which also contains the message to send,
+	The <c>MsgHdr</c> may also contain an list of optional <c>cmsghdr_send()</c>
+	(depends on what the protocol and platform supports).</p>
+
+	<p>Unlike the <seealso marker="#send/2"><c>send</c></seealso> function,
+	this one sends <em>one message</em>.
+	This means that if, for whatever reason, its not possible to send the
+	message in one go, the function will instead return with the
+	<em>remaining</em> data (<c>{ok, Remaining}</c>). Thereby leaving it
+	up to the caller to decide what to do (retry with the remaining data
+	of give up). </p>
+
+	<p>In the case when there is no room in the (system-) buffers,
+	the function will return with the <c>SelectInfo</c>. The caller
+	can then await a select message,
+	<c>{'$socket', Socket, select, Info}</c>
+	(where <c>Info</c> is the <c>select_ref()</c> from the
+	<c>SelectInfo</c>), when there is room for more data (a subsequent
+	call to sendmsg will then send the data). </p>
+      </desc>
+    </func>
+
+    <func>
       <name name="sendto" arity="3" since="OTP 22.0"/>
       <name name="sendto" arity="4" clause_i="1" since="OTP 22.0"/>
-      <name name="sendto" arity="4" clause_i="2" since="OTP 22.0"/>
-      <name name="sendto" arity="5" since="OTP 22.0"/>
+      <name name="sendto" arity="4" clause_i="3" since="OTP 22.0"/>
+      <name name="sendto" arity="5" clause_i="2" since="OTP 22.0"/>
       <fsummary>Send a message on a socket.</fsummary>
       <desc>
         <p>Send a message on a socket, to the specified destination.</p>
@@ -524,6 +767,23 @@
     </func>
 
     <func>
+      <name name="sendto" arity="4" clause_i="2" anchor="sendto_async" since="OTP @OTP-15731@"/>
+      <name name="sendto" arity="5" clause_i="1" since="OTP @OTP-15731@"/>
+      <fsummary>Send a message on a socket.</fsummary>
+      <desc>
+        <p>Send a message on a socket, to the specified destination.</p>
+
+	<p>In the case when there is no room in the (system-) buffers,
+	the function will return with the <c>SelectInfo</c>. The caller
+	can then await a select message,
+	<c>{'$socket', Socket, select, Info}</c>
+	(where <c>Info</c> is the <c>select_ref()</c> from the
+	<c>SelectInfo</c>), when there is room for more data (a subsequent
+	call to sendto will then send the data). </p>
+      </desc>
+    </func>
+
+    <func>
       <name name="setopt" arity="4" clause_i="1" since="OTP 22.0"/>
       <name name="setopt" arity="4" clause_i="2" since="OTP 22.0"/>
       <name name="setopt" arity="4" clause_i="3" since="OTP 22.0"/>
diff --git a/erts/doc/src/socket_usage.xml b/erts/doc/src/socket_usage.xml
index 4b3872d7e3..7e65bcbf70 100644
--- a/erts/doc/src/socket_usage.xml
+++ b/erts/doc/src/socket_usage.xml
@@ -34,11 +34,84 @@
     <title>Introduction</title>
     <p>The socket interface (module) is basically an "thin" layer on top of
     the OS socket interface. It is assumed that, unless you have special needs,
-    gen_[tcp|udp|sctp] should be sufficent. </p>
+    gen_[tcp|udp|sctp] should be sufficent (when they become available). </p>
     <p>Note that just because we have a documented and described option,
     it does <em>not</em> mean that the OS supports it. So its recommended
     that the user reads the platform specific documentation for the
     option used. </p>
+    <section>
+      <title>Asynchronous calls</title>
+      <p>Some functions allow for an <i>asynchronous</i> call
+      (<seealso marker="socket#accept_async"><c>accept/2</c></seealso>,
+      <seealso marker="socket#connect_async"><c>connect/3</c></seealso>,
+      <seealso marker="socket#recv_async"><c>recv/3,4</c></seealso>,
+      <seealso marker="socket#recvfrom_async"><c>recvfrom/3,4</c></seealso>,
+      <seealso marker="socket#recvmsg_async"><c>recvmsg/2,3,5</c></seealso>,
+      <seealso marker="socket#send_async"><c>send/3,4</c></seealso>,
+      <seealso marker="socket#sendmsg_async"><c>sendmsg/3,4</c></seealso> and
+      <seealso marker="socket#sendto_async"><c>sendto/4,5</c></seealso>).
+      This is achieved by setting the <c>Timeout</c> argument to
+      <c>nowait</c>. For instance, if calling the
+      <seealso marker="socket#recv_async"><c>recv/3</c></seealso>
+      function with Timeout set to <c>nowait</c> (i.e. 
+      <c>recv(Sock, 0, nowait)</c>)
+      when there is actually nothing to read, it will return with
+      <c>{ok, </c>
+      <seealso marker="socket#type-select_info"><c>SelectInfo</c></seealso><c>}</c>.
+      When data eventually arrives a 'select message'
+      will be sent to the caller:</p>
+      <taglist>
+	<!-- NOTE THAT THE EMPTY TAG IS INTENTIONAL -->
+	<tag></tag>
+	<item><c>{'$socket', socket(), select, select_ref()}</c></item>
+      </taglist>
+      <p>The caller can then make another
+      call to the recv function and now expect data.</p>
+      <p>The user must also be prepared to receive an abort message: </p>
+      <!--
+      <list type="ordered">
+	<item><c>{'$socket', Sock, abort, Info}</c></item>
+      </list>
+      -->
+      <taglist>
+	<!-- NOTE THAT THE EMPTY TAG IS INTENTIONAL -->
+	<tag></tag>
+	<item><c>{'$socket', socket(), abort, Info}</c></item>
+      </taglist>
+      <p>If the operation is aborted
+      for whatever reason (e.g. if the socket is closed "by someone else").
+      The <c>Info</c> part contains the abort reason (in this case that
+      the socket has been closed <c>Info = {select_ref(), closed}</c>). </p>
+      <p>Note that all other users are <em>locked out</em> until the
+      'current user' has called the function (recv in this case). So either
+      immediately call the function or
+      <seealso marker="socket#cancel/2"><c>cancel</c></seealso>. </p>
+
+      <p>The general form of the 'socket' message is: </p>
+      <taglist>
+	<!-- NOTE THAT THE EMPTY TAG IS INTENTIONAL -->
+	<tag></tag>
+	<item><c>{'$socket', Sock :: socket(), Tag :: atom(), Info :: term()}</c></item>
+      </taglist>
+      <p>Where the format of <c>Info</c> is a function of <c>Tag</c>:</p>
+      <table>
+	<row>
+	  <cell><em>Tag</em></cell>
+	  <cell><em>Info value type</em></cell>
+	</row>
+	<row>
+	  <cell>select</cell>
+	  <cell>select_ref()</cell>
+	</row>
+	<row>
+	  <cell>abort</cell>
+	  <cell>{select_ref(), Reason :: term()}</cell>
+	</row>
+	<tcaption>socket message info value type</tcaption>
+      </table>
+      <p>The <c>select_ref()</c> is the same as was received in the
+      <seealso marker="socket#type-select_info"><c>SelectInfo</c></seealso>. </p>
+    </section>
   </section>
 
   <section>