[CRIU] [PATCH cr 00/10] rework logic about lock/unlock network

Andrey Vagin avagin at openvz.org
Thu Sep 13 09:10:20 EDT 2012


Network should be locked before dumping and unlocked after restoring.

When a socket is going out from repair mode, it sends winprobe,
so network should be unlocked in this moment.

In addition this series adds two options to set lock/unlock scripts,
which are used to lock/unlock network in a target name space.

Andrey Vagin (10):
  restorer: unify log functions
  net: add ability to use tcp_repair_off from a restorer code
  tcp: unset TCP_REPAIR at the last moment after unlocking network
  nf: make nf_connection_switch_raw public
  crtools: add options for lock/unlock network scripts
  cd-dump: lock connection with iptables rules only in a current netns
  cr-dump: lock network before dump and unlock in case of errors
  cr-restore: add ability to unlock connections from a controll process
  cr-restore: unlock connections at the last moment
  netfilter: remove unused code

 cr-dump.c              |   39 ++++++++++++++++++-
 cr-restore.c           |   46 +++++++++++++++++-----
 crtools.c              |   10 +++++
 include/crtools.h      |    2 +
 include/netfilter.h    |    3 +-
 include/restorer-log.h |    5 +-
 include/restorer.h     |    3 +
 include/sk-inet.h      |   36 ++++++++++++++++-
 netfilter.c            |    8 +---
 restorer-log.c         |    4 +-
 restorer.c             |    7 ++-
 sk-inet.c              |   34 ++++++++++++++++
 sk-tcp.c               |   98 ++++++++++++++++++++++++++++++++++--------------
 13 files changed, 237 insertions(+), 58 deletions(-)



More information about the CRIU mailing list