Changes

Jump to navigation Jump to search
44 bytes removed ,  09:10, 7 September 2015
no edit summary
Line 5: Line 5:  
* Support for seccomp strict mode
 
* Support for seccomp strict mode
 
* Support for stream unix sockets inheritance
 
* Support for stream unix sockets inheritance
* Support for relative paths for unix sockets
   
* Support uid/gid-restricted mounts in userns
 
* Support uid/gid-restricted mounts in userns
 +
* Support deleted bind-mounts
 +
* Freezer cgroups can be used on dump to freeze fast-spawning processes
 +
* Ability to specify maximum ghost file size
 +
* OverlayFS support
 +
* Support relative unix sockets' bind paths
 
* In libcriu
 
* In libcriu
 
** New set of calls using non-global opts
 
** New set of calls using non-global opts
Line 13: Line 17:  
* Arch-specific improvements
 
* Arch-specific improvements
 
** Altivec and PSX support for PPC
 
** Altivec and PSX support for PPC
** PIEGEN (FIXME, how to declare it?)
+
** Small PIE loader
 
** Preparations for 32-bit x86
 
** Preparations for 32-bit x86
   Line 37: Line 41:  
* Weird paths on tmpfs caused tar to fail
 
* Weird paths on tmpfs caused tar to fail
 
* Temporary cgroup mount set (cgyard) got propagated into the host tree
 
* Temporary cgroup mount set (cgyard) got propagated into the host tree
* Crash when restoring netns from older images
   
* Restore of inherited shared pipe failed
 
* Restore of inherited shared pipe failed
 
* Spaces, tabs and backslashes in mountpoints' paths caused dump to fail
 
* Spaces, tabs and backslashes in mountpoints' paths caused dump to fail
 
* Tmpfs mounted with empty source caused dump to fail
 
* Tmpfs mounted with empty source caused dump to fail
* Race between unix sockets' connect and listen may cause restore to fail
  −
* Multiple unix datagram clients restored server queue multiple times
   
* The criu.pc file contained bad version when built from tarball
 
* The criu.pc file contained bad version when built from tarball
 
* Deprecated -n option found in docs
 
* Deprecated -n option found in docs
 
* On aarch64 the maximum virtual address available for user-space was wrongly hardcoded
 
* On aarch64 the maximum virtual address available for user-space was wrongly hardcoded

Navigation menu