Download/criu/2.x

This page lists older (2.x) CRIU releases. For latest release, see Download/criu.

With 2.x, we decided to make several technologies available as standalone projects (e.g. Compel) and release new stuff faster than once every 3 months (see release schedule).

v. 2.12Edit

Tarball: criu-2.12.tar.bz2
Version: 2.12 "Vulcanite Rook"
Released: 8 Mar 2017
GIT tag: v2.12

New featuresEdit

  • C/R of
    • external TTYs (for Docker C/R)

Optimizations/improvementsEdit

  • Sanitized the way the -v works

FixesEdit

  • Checking features via RPC crashed
  • Resting pipes in user-namespaces could fail on modern kernels
  • Shutdown state for UNIX sockets could be lost on restore
  • Dump of huge (over 2Gb) SysV shmem segments didn't work


v. 2.11.1Edit

Tarball: criu-2.11.1.tar.bz2
Version: 2.11.1
Released: 17 Feb 2017
GIT tag: v2.11.1

FixesEdit

  • Page server start via RPC was broken
  • Fedora build didn't work
  • Ppc64LE restorer switch crashed


v. 2.11Edit

Tarball: criu-2.11.tar.bz2
Version: 2.11 "Acrylic Bullfinch"
Released: 13 Feb 2017
GIT tag: v2.11

New featuresEdit

Optimizations/improvementsEdit

  • More strict checks for extra CLI options
  • Report errors when probing locks
  • Restorer logs now contain timestamps

FixesEdit

  • Regression: v2.10 was broken on ARM
  • Use-after-free when restoring ghost directory
  • Array out-of-bound access when restoring VETH device
  • Page server exit code could be screwed up
  • Clang over-optimized string.h routines resulting in random crashes
  • Parasite failed to send FDs via socket on Alpine Linux
  • Restore of huge file tables could get stuck
  • Restore of epoll in epoll could fail
  • Errno value could be lost when reporting failure to restore invisible files
  • Dump of sched params didn't work on Alpine
  • Restore of huge memory dumps (over 2G) failed
  • Installation guessed /lib vs /lib64 with errors
  • Migration between xsave and noxsave didn't work for wrong cpu feature being checked


v. 2.10Edit

Tarball: criu-2.10.tar.bz2
Version: 2.10 "Brass Waxwing"
Released: 16 Jan 2017
GIT tag: v2.10

New featuresEdit

Optimizations/improvementsEdit

  • Logs cleaned up (removed bunch of useless, fixed '\n' in perrors)
  • Action scripts errors are printed in logs
  • Removed several iovec-s copying over the pagemap code
  • Restore degraded linearly on Xen guests. Breakpoints disabled until solution

FixesEdit

  • Py bindings fault on restore error delivery
  • Fd leaked on file restore error path
  • Fd leaked when restoring invisible files (gets closed with criu exit though)
  • Link remap restore could fail on kernels 4.8 and higher
  • Impossible to restore after restore error with link remap file in images
  • When going daemon a descriptor could be leaked
  • Custom setting of mmap_min_addr could make restore to fail
  • Sending pages over UNIX socket could race and fail with EAGAIN
  • Error getting ID of /proc/pid/ns/foo link not propagated and could result in bogus NS ID generated


v. 2.9Edit

Tarball: criu-2.9.tar.bz2
Version: 2.9 "Silk Tit"
Released: 12 Dec 2016
GIT tag: v2.9

New featuresEdit

  • CRIU can now be built with clang on all supported architectures
  • Ignore missing sysctls on restore with --weak-sysctl
  • C/R overmounted mountpoints

Optimizations/improvementsEdit

  • Batch restore of memory contents from pages.img files
  • Link-remap type for invisible files is explicit in images
  • Man page for CRIT

FixesEdit

  • C/R with --empty-ns still handled iptables configuration
  • SCM messages inside UNIX socket got lost after C/R (now dump aborted)
  • Empty unixsk.img file appeared when dumping tasks without unix sockets
  • Install procedure wasn't PEP-394 compliant
  • CRIU blocking netfilter rules were added at the tail of the chain resulting in unlocked TCP connections
  • Dump/Restore spurious failures when open() returned 0 descriptor
  • When dumping shmem lots of zero pages were written into image files
  • Ghost directory with more than zero ghost parents caused restore to fail
  • Shared mount could escape to different group on restore


v. 2.8Edit

Tarball: criu-2.8.tar.bz2
Version: 2.8 "Bronze Siskin"
Released: 14 Nov 2016
GIT tag: v2.8

New featuresEdit

Optimizations/improvementsEdit

  • x86 can now be built with clang
  • When dumping files useless garbage was sent with descriptors from parasite
  • The clear_tid_address and regs are printed in hex with CRIT
  • Big code rework for compel (part 1)
  • Removed duplicate error messages from opening /proc files

FixesEdit

  • Restoring cgroup NS could use old path prefix
  • criu check crashed on btrfs mounts
  • RO external mounts in userns couldn't be restored
  • Unmounted on host binfmt_misc could cause dump to fail
  • Off-by-one could cause criu crash when dumping shared / bind-mount
  • Mount namespace' roots could have flags changed on restore
  • Dying tasks could erroneously be tried to dump
  • Swapped shared memory pages were not dumped
  • Errno value can be sometimes spoiled by RPC
  • Restore of netns with newer iproute2 tool could fail

DeprecatedEdit


v. 2.7Edit

Tarball: criu-2.7.tar.bz2
Version: 2.7 "Rubber Owl"
Released: 17 Oct 2016
GIT tag: v2.7

New featuresEdit

  • Option --cgroup-root now makes sense on dump too
  • CLOCK_BOOTTIME timer supported

Optimizations/improvementsEdit

  • Output of iptables command leaked into logs for no use
  • Helper dev environment installation script for Debian
  • Man-page updated and prettifiedĀ :)

FixesEdit

  • Unmounted binfmt_misc with rules wasn't dumped at all
  • Malloc() error could result in crash
  • Device cgroup restore could fail restoring empty record
  • Some entries in device cgroups were restored twice
  • Potential crash when dumping cgroup bindmounts
  • Sign error caused dump to fail on btrfs partitions
  • Shared mounts with the same mount path failed the dump
  • Threads were restored with unshared FS (cwd and root)
  • Shared memory changes tracking disabled (regression found)
  • Restore of autofs can hang
  • LSM profile propagation could be lost
  • Mountpoint with lots of options blocked the dump (too small buffer for parsing)
  • External slave mount (with external master) blocked the dump
  • Mounts with STRICTATIME restored with others flags dropped

DeprecatedEdit

  • No reg-file entry for TTYs


v. 2.6Edit

Tarball: criu-2.6.tar.bz2
Version: 2.6 "Paper Crane"
Released: 12 Sep 2016
GIT tag: v2.6

New featuresEdit

Optimizations/improvementsEdit

  • Use service FD for transport sockets on restore
  • Ability to turn pagemap-cache off (some kernels are buggy)
  • The criu --help text has become better

FixesEdit

  • R/O-mounted root could block the dump
  • Restore of cgroup.mm.oom_control could fail
  • Cgroup fs bind mounts were detected with error
  • Unaligned futex-es in parasite could cause dump to crash
  • When compiled with gcc-4.9 parasite code crashed
  • Failure to freeze cgroup didn't result in aborting of dump
  • Wrong ns list was parsed when dumping userns (invisible since nesting works only for mntns)
  • Non-inheritable non-tty as stdin caused shell-job restore to erroneously fail
  • Error path in criu dedup could crash

DeprecatedEdit

  • Per-pid rlimit, itimers and posix-timers
  • Separate image for epoll tfds (target file descriptors)


v. 2.5Edit

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


v. 2.4Edit

Tarball: criu-2.4.tar.bz2
Version: 2.4 "Marble Lark"
Released: 11 Jul 2016
GIT tag: v2.4

New featuresEdit

  • Generate core from images
  • Ability to forcibly drop half-open TCP connections on C/R
  • Ability to specify cgroup ctls to dump via API
  • Opened/mapped files' mode is compared between dump and restore times
  • C/R of
    • AutoFS mountpoints
    • New cgroups (perf_event, net_cls, net_prio and pids)
    • Memcgroup optional properties
    • Devices cgroup

Optimizations/improvementsEdit

  • Pagemap image entries are cached in memory

FixesEdit

  • Configured kmem cgroup limit restore failed
  • Mem cgroup oom_control
  • Cgroup's pids.max was not C/R-ed
  • Failure to write cgroup property was ignored
  • No init PID in pre-dump action script
  • Sigactions inheritance didn't work on ARM
  • Opened "/proc" dir blocked the dump
  • Working with iptables was racy
  • Sibling mounts detection error on dump
  • Devconf accept_redirects devconf could be restored with errors
  • "All" devconfs could be overridden by "Default"
  • Name-less unix sockets got auto-bound
  • Mode was lost for PTY device file on restore
  • Newer protobuf compilers didn't recognize PB files
  • External mounts could be remounted with MS_PRIVATE
  • Build fail on Alpine Linux

Deprecated/removedEdit

  • Per-pid file locks images
  • Per-pid fdinfo images
  • Ancient pagemap/pages images


v. 2.3Edit

Tarball: criu-2.3.tar.bz2
Version: 2.3 "Wooden Duck"
Released: 14 Jun 2016
GIT tag: v2.3

New featuresEdit

  • Ability not to show payload for some objects in CRIT
  • Pidfile is written at the end of restore
  • Ability to join existing namespaces on restore
  • C/R of
    • Data sitting in TTYs
    • Partially write-protected SysVIPC segments
    • Debugfs and tracefs mounts
    • Overmounted tmpfs
    • IPv6 devconf sysctls
    • External block devices
    • Unix sockets with mismatched shutdown state

Optimizations/improvementsEdit

  • Relaxed calculation of AIO ring size
  • Tree-based search of tasks by real pid
  • Less mem-to-mem copies on restore
  • Saner devconf image format
  • More verbose explanation of why task cannot be seized
  • PID is printed in PIE logs

FixesEdit

  • Too many mmap-ed files blocked the dump
  • Potential memory corruption when working with IPv6 sockets
  • Overmounted bind mounts could cause restore to fail
  • Overmounted bind mounts could result in badly restored mount tree
  • Incomplete restoration of RO bind mounts options

Deprecated/removedEdit

  • Greedy mode of pagemap (non-root) caused dump to fail (disabled)


v. 2.2Edit

Tarball: criu-2.2.tar.bz2
Version: 2.2 "Carbon Nightingale"
Released: 16 May 2016
GIT tag: v2.2

New featuresEdit

  • Uninstall action in Makfilefile
  • "Post-resume" added to action scripts
  • Root task's PID in environment for action scripts
  • C/R of
    • Devconfs drop_gratuitous_arp and drop_unicast_in_l2_multicast
  • * Serial ttys

Optimizations/improvementsEdit

  • Lighter link-remaps restore on newer kernels

FixesEdit

  • Race when restoring userns vs setting ns' maps
  • Tasks with zero fds failed the dump
  • Restore of TCP recv queue could fail due to kernel mem alloc constraints
  • No errors were written to logs when launching helper (tar/iptables) app in userns restore
  • User-mode dumped no memory pages sometimes
  • Bind mounts considered not as bind sometimes
  • Two mounts in the same directory blocked the dump
  • Off-by in on /dev/tty{1,63} dumping
  • Forking of cgroupns task was done with screwed clone flags

Deprecated/removedEdit

  • Greedy mode of pagemap dumping (on some kernels we do not support user-mode)
  • Removed the --namespaces option


v. 2.1Edit

Tarball: criu-2.1.tar.bz2
Version: 2.1 "Steel Lapwing"
Released: 11 Apr 2016
GIT tag: v2.1

New featuresEdit

  • Checking now classifies features to important/extra/experimental
  • Ability to bring some disk files into images. See $source/scripts/tmp-files.sh
  • C/R of
    • Completed AIO requests
    • Fallback gre and gretap net devices

Optimizations/improvementsEdit

  • Code coverage collecting now works
  • Use native rtnl library for netlink messages processing
  • Using --output - now results in stdout as log, not a file with the name "-"
  • Signals are printed by names in logs

FixesEdit

  • Make tar generated tarbal with bad name
  • CG restore code lacked rollback in some places
  • Error code from raw syscalls was treated with errors resulting in wrong criu check reports
  • Dumping task with HUGE amount of file descriptors failed
  • Task could be stopped after pre-dump if respective option was used
  • A /proc/pid directory from dead process conflicting with a new alive one could cause dump to fail
  • Zombie from alien session/process group caused restore to fail
  • CGroup fs was wrongly mounted in CGNS on restore
  • Irmap scan was mis-checking devices numbers
  • Use-after-free in irmap scan
  • Btrfs bindmounts detection was mistaken due to 'subvol=' options met
  • Propagation of mountpoint's shared groups was lost for propagated mounts
  • Unaligned allocations of restore shared memory could result in codedumps when used by futexes
  • Temporary mountpoints could result in spurious propagations
  • When aborting the dump criu could crash on use-after-free objects
  • Locking the network could stuck doing the DNS resolve
  • Several build fixes

Deprecated/removedEdit

  • The images from criu prior to 0.4 are deprecated
  • The --namespaces option makes no sense and is also deprecated
  • The --ms option for check action is deprecated


v. 2.0Edit

Tarball: criu-2.0.tar.bz2
Version: 2.0
Released: 7 Mar 2016
GIT tag: v2.0

New featuresEdit

  • New code layout for sub-projects (e.g. Compel)
  • Unprivileged dump
  • Dump/check cpuinfo support for PPC
  • Explorers for CRIT
  • Added "post-setup-namespaces" to action scripts
  • Added timeout for dump procedure (5 sec by default)
  • Ability to override LSM profile on restore with CLI/RPC option
  • External bind mounts can be fs-root mounts too
  • Skip netns' internals on dump and restore (for Docker integration)
  • Advanced support for external files
  • C/R for
    • Mode and uid/gid of cgroup files and dirs
    • Freeze cgroup state (frozen/thawed)
    • Task's loginuid and oom score
    • Per-thread credentials
    • Filter mode of seccomp
    • Ghost file in removed directory
    • Ghost files lutimes
    • Binfmt-misc FS contents
    • Netfilter conntracks and expectations
    • Multi-headed cgroups
    • CGroup namespaces (no nesting)

Optimizations/improvementsEdit

  • Align parasite stack on 16 bits for correctness
  • Compilation with native libc syscall wrappers and helpers
  • Parasite code injection done via memfd system call
  • Make vaddr to pfn conversion with one less syscall
  • CRIT shows device numbers in "maj:min" manner
  • CRIT shows mmap's status in verbose
  • Docker files for builds on all supported arches

FixesEdit

  • Absent readlink syscall on ARM (use readlinkat instead) could cause dump to fail
  • Wrong argument to timer_create system call could cause restore to crash
  • Extra tasks in freeze cgroup caused dump to fail/hand/crash
  • Unaligned restore-time object allocations caused lock operations to fail
  • Opened /proc/pid dir of dead task failed the dump
  • Unaligned stacks caused criu to fail on aarch64
  • Changed device numbers on restore side could cause random failures
  • Fixes in mount points sharing/slavery/propagation restore
  • Race between mntns creation and fds closing in different tasks could cause restore to fail
  • Hard kernel limit on TCP repair recv queue restore could cause big queue restore to fail
  • Unconnected dgram UNIX socket with data lost packets on restore
  • CRIT didn't show IPC objects
  • CRIT didn't convert IP addresses in images
  • Logs from PIE code contained corrupted addresses and sizes
  • Not loaded netfilter modules could cause dump/restore to stuck on dumping netlink socket
  • Shared external mounts were restored with error

SecurityEdit

  • User-mode
  • When checking for namespaces' CRIU entered userns with host creds

Deprecated/removedEdit

  • Completely removed 'show' action. Use CRIT instead.


See alsoEdit