Difference between revisions of "Sockets"

From CRIU
Jump to navigation Jump to search
m (categorized)
Line 16: Line 16:
  
 
[[Category:Under the hood]]
 
[[Category:Under the hood]]
 +
[[Category:Files]]
 +
[[Category:Network]]

Revision as of 15:48, 26 February 2015

Unix sockets initial support

Currently we support Unix socket of all kinds, UDP both IPv4 and IPv6, TCP in Listen and (!) Established states and Netlink ones.

The cpt part uses the sock_diag engine to collect extended information about socket, then CRIU uses the files dumping engine to get access to sockets state.

The restore part of Unix sockets is the most tricky part. Listen sockets are just restored, this is simple. Connected sockets are restored like this:

  1. One end establishes a listening anon socket at the desired descriptor;
  2. The other end just creates a socket at the desired descriptor;
  3. All sockets, that are to be connect()-ed call connect. Unix sockets do not block connect() till the accept() time and thus we continue with...
  4. ... all listening sockets call accept() and ... dup2 the new fd into the accepting end.

There's a problem with this approach -- socket names are not preserved, but looking into our OpenVZ implementation I think this is OK for existing apps.