[CRIU] [PATCH 2/3] mem: if no parent image persists, can't rely on it

[Pavel Emelyanov]

On 04/15/2014 04:48 PM, Pavel Tikhomirov wrote:
> It seem to me, that clear_soft_dirty function for pte in kernel is called only
> if we had explicit write to /proc/pid/clear_refs. Only after that all pages will
> become write-protected and dirty tracking realy works, if new process was
> created between snapshots, some part of its memory can be not write
> protected so no PF generated for this part and some soft-dirty bits not set,
> isn't it?

When a new process is created all its memory is COW-ed from parent and
thus write-protected. All _new_ mappings will get VM_SOFT_DIRTY flag.

Thanks,
Pavel