Jump to: navigation, search


438 bytes added, 20:54, 12 August 2018
no edit summary
=== Potential memory corruption ===
When processes are dumped and restored on different cpu, the application may have remembered frame size on its own somewhere inside own code and in worst scenarioit may allocate memory with size less than needed on different cpu, so the next call to <code>xsave</code> silently overwrite memory leading to sigsegv in best caseCurrent criu implementation check for <code>cpuinfo</code> images to be compatible and size and features required to match.In turn some OS may mask some of the features with cpuid faulting engine but still all cpus in the pool should report same maximal size of the frame.

Navigation menu