Difference between revisions of "Download/criu/1.5"

From CRIU
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 32: Line 32:
 
* Wrong /proc was used when reading the list of FDs to close on restore
 
* Wrong /proc was used when reading the list of FDs to close on restore
 
* Race in restoring TCP established and listening sockets results in failed bind() on the latter
 
* Race in restoring TCP established and listening sockets results in failed bind() on the latter
 +
* Legacy ttys errorneously treated as unix98
 +
* TTY pairs slavery setup could pick wrong peer
 +
* For user-dump the log and pid files still belonged to root
 +
* Task could die while being frozen thus causing dump to fail or save wrong task state
 +
* Failures in mount points validation and sharing resolving didn't abort the dump (error arose on restore)

Latest revision as of 08:48, 25 February 2015

Tarball: criu-1.5.tar.bz2
Version: 1.5
Released: 2 Mar 2015
GIT tag: v1.5

New features[edit]

  • CRIT tool
  • Ability to request CPU compatibility on instructions level only
  • C/R of empty AIO rings
  • More detailed errno report via RPC
  • Per-feature "criu check"
  • Inheriting FDs on restore
  • Ability to automatically move veth device to host-side bridge on netns restore
  • VT terminals support
  • More user namespaces C/R stuff

Optimizations[edit]

  • TCP send queue is restored in the maximal portions allowed by the kernel
  • Pre-loading sock-diag modules now happens in a more elegant way

Fixes[edit]

  • Multi-threaded tasks on 64bit ARM could segfault upon restore
  • When doing "check" CRIU could leave un-killed piggie task
  • The --cpu-cap option argument was parsed with errors
  • Incorrect handling of --cpu-cap fpu compatibility mode on restore
  • Criu ignored trailing CLI arguments that resulted in usage confusions
  • Irmap hints didn't include common "/" path
  • When run per user request, CRIU left log and pid files belonging to root
  • Mappings on AUFS could be looked up on wrong mount point
  • Fixed compilation on Centos6.5
  • Wrong /proc was used when reading the list of FDs to close on restore
  • Race in restoring TCP established and listening sockets results in failed bind() on the latter
  • Legacy ttys errorneously treated as unix98
  • TTY pairs slavery setup could pick wrong peer
  • For user-dump the log and pid files still belonged to root
  • Task could die while being frozen thus causing dump to fail or save wrong task state
  • Failures in mount points validation and sharing resolving didn't abort the dump (error arose on restore)