Difference between revisions of "Download/criu/3.6"

From CRIU
Jump to: navigation, search
m (typos)
Line 15: Line 15:
 
* Overflow when parsing autofs info from /proc file
 
* Overflow when parsing autofs info from /proc file
 
* Dumps of anon [[shared memory]] with sysvipc one raced with each other clashing and corrupting image file names
 
* Dumps of anon [[shared memory]] with sysvipc one raced with each other clashing and corrupting image file names
* The "dumpable" flag was not restore on shmem regions
+
* The "dumpable" flag was not restored on shmem regions
 
* Trash bits leaked into image when dumping [[fsnotify]] on some kernels
 
* Trash bits leaked into image when dumping [[fsnotify]] on some kernels
 
* Lock/unlock of iptables from different criu processes raced with each other
 
* Lock/unlock of iptables from different criu processes raced with each other
 
* Closed [[TCP connection]] with non-empty send queue blocked the dump
 
* Closed [[TCP connection]] with non-empty send queue blocked the dump
* When {{Opt|--empty-ns}} for netns was set on dump ''only'', the restore failed (Docker case)
+
* When {{Opt|--empty-ns}} for netns was set on dump ''only'', restore failed (Docker case)

Revision as of 23:35, 4 December 2017

Tarball: criu-3.6.tar.gz
Version: 3.6 "Alabaster Finch"
Released: 23 Oct 2017
GIT tag: v3.6

New features

  • C/R for
    • Files (except for unix sockets, ttys and epolls) sent over unix sockets
    • Threads with different creds
    • Ipv6 over ipv4 tunnel (SIT device)

Improvements

  • Tests are now run in Alpine and Fedora-rawhide

Bugfixes

  • Some s390x registers were not restored by native sigrestore way
  • Overflow when parsing autofs info from /proc file
  • Dumps of anon shared memory with sysvipc one raced with each other clashing and corrupting image file names
  • The "dumpable" flag was not restored on shmem regions
  • Trash bits leaked into image when dumping fsnotify on some kernels
  • Lock/unlock of iptables from different criu processes raced with each other
  • Closed TCP connection with non-empty send queue blocked the dump
  • When --empty-ns for netns was set on dump only, restore failed (Docker case)