Difference between revisions of "Download/criu/2.5"

m
(no need to explicitly specify the codename now)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Release|2.5|15 Aug 2016|Concrete oriole}}
+
{{Release|2.5|15 Aug 2016}}
  
 
=== New features ===
 
=== New features ===
Line 18: Line 18:
 
* TCP window could remain clamped after restore resulting in connection lockup/slowdown
 
* TCP window could remain clamped after restore resulting in connection lockup/slowdown
 
* Dump could stuck when injecting a parasite
 
* Dump could stuck when injecting a parasite
* The --timeout option wasn't taken into account when freezing tasks using freezecg
+
* The {{Opt|--timeout}} option wasn't taken into account when freezing tasks using freezecg
 
* Race in freezeing/seizing could result in lost tasks
 
* Race in freezeing/seizing could result in lost tasks
 
* Memory leaks here and there on error paths
 
* Memory leaks here and there on error paths
 
* Double free in xvstrcat (crash)
 
* Double free in xvstrcat (crash)
 
* VDSO length was mis-calculated
 
* VDSO length was mis-calculated
* Symlink on --root path could make restore erroneously fail
+
* Symlink on {{Opt|--root}} path could make restore erroneously fail
 
* Potential memory corruption on reading mntns images
 
* Potential memory corruption on reading mntns images
 
* When restoring on systems with low pid_max limit restore could fail
 
* When restoring on systems with low pid_max limit restore could fail

Latest revision as of 08:16, 26 January 2017

Tarball: criu-2.5.tar.bz2
Version: 2.5 "Concrete Oriole"
Released: 15 Aug 2016
GIT tag: v2.5

New featuresEdit

  • C/R
    • fs.mqueue.msg*_default sysctls
    • Unix sockets with overwritten paths
    • Link-remap files in removed directories

Optimizations/improvementsEdit

  • Micro-optimization on namespace ID evaluation
  • Restoring shared files uses one socket instead of per-fd ones
  • More verbosity when refusing to dump a file descriptor

FixesEdit

  • Restore could fail on openat() with ENXIO when multiple mnt namespaces get restored
  • The criu exec action got broken
  • Link-remap and ghost files remained on FS after restore failure
  • TCP window could remain clamped after restore resulting in connection lockup/slowdown
  • Dump could stuck when injecting a parasite
  • The --timeout option wasn't taken into account when freezing tasks using freezecg
  • Race in freezeing/seizing could result in lost tasks
  • Memory leaks here and there on error paths
  • Double free in xvstrcat (crash)
  • VDSO length was mis-calculated
  • Symlink on --root path could make restore erroneously fail
  • Potential memory corruption on reading mntns images
  • When restoring on systems with low pid_max limit restore could fail
  • RO-protected SysV shmem segments could be restored with PROT_EXEC
  • File mode of mapped file was evaluated with errors
  • Restore of cgroups' mem.swappines and ..use_hierarchy blocked sub-groups creation
  • Impossible to restore cgoup mem.swappines default value
  • Zombies living in orphan sessions/groups failed the restore