Difference between revisions of "TCP connection"

From CRIU
Jump to: navigation, search
(Undo revision 340 by 91.121.27.33 (talk))
(fixed first half of the article)
Line 1: Line 1:
This page describes how we handle established TCP connections
+
This page describes how we handle established TCP connections.
  
 
== TCP repair mode in kernel ==
 
== TCP repair mode in kernel ==
  
The sockoption called TCP_REPAIR was recently added to the kernel and helps with doing C/R for TCP sockets.
+
The <code>TCP_REPAIR</code> socket option was added to the kernel 3.5 to help with C/R for TCP sockets.
  
When set this option turn the socket into a special state in which any action performed on it doesn't
+
When this option is used, a socket is switched into a special mode, in which any action performed on it
result in any defined by protocol actions, but instead directly puts the socket into a state, which
+
does not result in anything defined by an appropriate protocol actions, but rather directly puts the socket
should be at the end of the successfully finished operation.
+
into a state, in which the socket is expected to be at the end of the successfully finished operation.
  
E.g. calling connect() on a repaired socket just switches one to the ESTABLISHED state with the peer set as requested.
+
For example, calling <code>connect()</code> on a repaired socket just changes its state to <code>ESTABLISHED</code>,
The bind() call forcibly binds the socket to a given address (ignoring any potential conflicts). Close()-ing the
+
with the peer address set as requested.
socket under repair happens without any transient FIN_WAIT/TIME_WAIT/etc states. Socket is silently killed.
+
The <code>bind()</code> call forcibly binds the socket to a given address (ignoring any potential conflicts).
 +
The <code>close()</code> call closes the socket without any transient <code>FIN_WAIT</code>/<code>TIME_WAIT</code>/etc states,
 +
socket is silently killed.
  
 
=== Sequences ===
 
=== Sequences ===
  
In order to restore the connection properly only binding and connecting it is not enough. One also needs to restore the
+
To restore the connection properly, bind() and connect() is not enough. One also needs to restore the
TCP sequence numbers. To do so the TCP_REPAIR_QUEUE and TCP_QUEUE_SEQ options were introduced.
+
TCP sequence numbers. To do so, the <code>TCP_REPAIR_QUEUE</code> and <code>TCP_QUEUE_SEQ</code> options were introduced.
  
The former one selects which queue (input or output) will be repaired and the latter gets/sets the sequence. Note, that
+
The former one selects which queue (input or output) will be repaired and the latter gets/sets the sequence. Note
 
setting the sequence is only possible on CLOSE-d socket.
 
setting the sequence is only possible on CLOSE-d socket.
  

Revision as of 11:13, 27 July 2012

This page describes how we handle established TCP connections.

TCP repair mode in kernel

The TCP_REPAIR socket option was added to the kernel 3.5 to help with C/R for TCP sockets.

When this option is used, a socket is switched into a special mode, in which any action performed on it does not result in anything defined by an appropriate protocol actions, but rather directly puts the socket into a state, in which the socket is expected to be at the end of the successfully finished operation.

For example, calling connect() on a repaired socket just changes its state to ESTABLISHED, with the peer address set as requested. The bind() call forcibly binds the socket to a given address (ignoring any potential conflicts). The close() call closes the socket without any transient FIN_WAIT/TIME_WAIT/etc states, socket is silently killed.

Sequences

To restore the connection properly, bind() and connect() is not enough. One also needs to restore the TCP sequence numbers. To do so, the TCP_REPAIR_QUEUE and TCP_QUEUE_SEQ options were introduced.

The former one selects which queue (input or output) will be repaired and the latter gets/sets the sequence. Note setting the sequence is only possible on CLOSE-d socket.

Packets in queue

When set the queue to repair as described above, one can call recv or send syscalls on a repaired socket. Both calls result on peeking or poking data from/to the respective queue. This sounds funny, but yes, for repaired socket one can receve the outgoing and send the incoming queues. Using the MSG_PEEK flag for recv is required.

Options

There are 4 options that are negotiated by the socket at the connecting stage. These are

  • mss_clamp -- the maximum size of the segment peer is ready to accept
  • snd _scale -- the scale factor for a window
  • sack -- whether selective acks are permitted or not
  • tstamp -- whether timestamps on packets are supported

All four can be read with getsockopt calls to a socket and in order to restore them the TCP_REPAIR_OPTIONS sockoption is introduced.

Checkpoint and restore TCP connection

With the above sockoptions dumping and restoring TCP connection becomes possible. The crtools just reads the socket state and restores it back letting the protocol resurrect the data sequence.

One thing to note here -- while the socket is closed between dump and restore the connection should be "locked", i.e. no packets from peer should enter the stack, otherwise the RST will be sent by a kernel. In order to do so a simple netfilter rule is configured that drops all the packets from peer to a socket we're dealing with. This rule sits in the host netfilter tables after the crtools dump command finishes and it should be there when you issue the crtools restore one.

That said, the command line option --tcp-established should be used when calling crtools to explicitly state, that the caller is aware of this "transitional" state of the netfilter.