Commits
Alexey Kuznetsov authored and Pavel Emelianov committed 6ecc6e3d844
[CPT] prevent changes of VM after VE was checkpointed It is possible that processes' VM is changed after VE is checkpointed and killed. At the moment it will happen when a process set clear_parent_tid or robust list pointers. It was not considered a problem, because VM is about to be destroyed in any case. But one case was missed: corresponging VM areas could be mapped to a file. If it is not deleted, the change will reach file system and migrate. Oops. F.e. shared locked futex will be unlocked after migration. (glibc tst-robust8 test)