2,257
edits
Changes
Jump to navigation
Jump to search
Line 23:
Line 23: − + + Line 30:
Line 31: + + + + + +
no edit summary
* Multi-threaded tasks on 64bit ARM could segfault upon restore
* Multi-threaded tasks on 64bit ARM could segfault upon restore
* When doing "check" CRIU could leave un-killed piggie task
* When doing "check" CRIU could leave un-killed piggie task
* The --cpu-cap option: argument was parsed with errors, incorrect handling of 'fpu' option in restore mode.
* The --cpu-cap option argument was parsed with errors
* Incorrect handling of --cpu-cap fpu compatibility mode on restore
* Criu ignored trailing CLI arguments that resulted in usage confusions
* Criu ignored trailing CLI arguments that resulted in usage confusions
* Irmap hints didn't include common "/" path
* Irmap hints didn't include common "/" path
* Fixed compilation on Centos6.5
* Fixed compilation on Centos6.5
* Wrong /proc was used when reading the list of FDs to close on restore
* Wrong /proc was used when reading the list of FDs to close on restore
* Race in restoring TCP established and listening sockets results in failed bind() on the latter
* Legacy ttys errorneously treated as unix98
* TTY pairs slavery setup could pick wrong peer
* For user-dump the log and pid files still belonged to root
* Task could die while being frozen thus causing dump to fail or save wrong task state
* Failures in mount points validation and sharing resolving didn't abort the dump (error arose on restore)