Overview
Request 389858 accepted
- Update to criu 2.1:
New features:
* Checking now classifies features to important/extra/experimental
* Ability to bring some disk files into images.
* C/R of Completed AIO requests and fallback gre and gretap net
devices
Optimizations/improvements:
* 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
Fixes:
* 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
Request History
tiwai created request
- Update to criu 2.1:
New features:
* Checking now classifies features to important/extra/experimental
* Ability to bring some disk files into images.
* C/R of Completed AIO requests and fallback gre and gretap net
devices
Optimizations/improvements:
* 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
Fixes:
* 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
tiwai accepted request
OK.