Difference between revisions of "Download/criu/3.8"

From CRIU
Jump to navigation Jump to search
 
(2 intermediate revisions by one other user not shown)
Line 5: Line 5:
  
 
* C/R of
 
* C/R of
** multiple network namespaces
+
** Multiple network namespaces
** allow to dump overmounted tmpfs mounts
+
** Overmounted tmpfs mounts
** allow to send unix sockets and epoll descriptors in scm messages
+
** Unix [[sockets]] and epoll descriptors in SCM messages
  
 
=== Improvements ===
 
=== Improvements ===
* rework service descriptors
+
* Rework [[service descriptors]] not to cause fdtable enormous grows
* start testing lazy migration
+
* Start testing [[lazy migration]] in Jenkins/Travis
  
 
=== Bugfixes ===
 
=== Bugfixes ===
* workaround Skylake kernel bug
+
* FP state wasn't reported on Skylake due to [https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1318800.html a kernel bug]
* fix gcc-8 warnings
+
* When compiled with gcc-8 a lot of warnings popped up
* fix lazy-migragion
+
* Resource leaked on error paths
* fix resource leaks on error paths
+
* Attributes of sit devices with value 0 were not saved into images (and were restored into default values)
* save all attributes for sit devices
+
* Tasks with pgid of a zombie hung the resture
 +
* [[Invisible files|Ghost files]] on RO bind-mounts of an RW mount couldn't be restored
 +
* Random memory corruptions during [[lazy migration|lazy restore]]

Latest revision as of 12:42, 13 March 2018

Tarball: criu-3.8.tar.gz
Version: 3.8 "Snow Bunting"
Released: 13 Mar 2018
GIT tag: v3.8

New features[edit]

  • C/R of
    • Multiple network namespaces
    • Overmounted tmpfs mounts
    • Unix sockets and epoll descriptors in SCM messages

Improvements[edit]

Bugfixes[edit]

  • FP state wasn't reported on Skylake due to a kernel bug
  • When compiled with gcc-8 a lot of warnings popped up
  • Resource leaked on error paths
  • Attributes of sit devices with value 0 were not saved into images (and were restored into default values)
  • Tasks with pgid of a zombie hung the resture
  • Ghost files on RO bind-mounts of an RW mount couldn't be restored
  • Random memory corruptions during lazy restore