[CRIU] [PATCHv2 00/17] Compatible C/R patches set, part 1

[Dmitry Safonov]

On 04/18/2016 09:20 PM, Pavel Emelyanov wrote:
> OK, the rest applied.
>
> What would be the next step?

How I see it:
o  Patches for moving vdso image for 32-bit with
mremap (I need them to set proper landing on
returning from syscall to vdso page) are done and
got acked from Andy - so get them mainstreamed.
o  I'm working on patches to change vdso blob from
native to compat. We have on restore stage 32-bit
vdso dumped previously on dump stage, but I need
them because one may restore application on
a different kernel, so 32-bit vdso will differ and in
that case I need to place jump trampolines to a new
vdso (like it works for non-compat now). That's why
I need API to remap 32-bit vdso blob on 64-bit target
(even though I have vdso blob's image on restore).
I hope, on this week I'll got acks on them.
o  Drop TIF_IA32 flag checks in kernel at least for
ptrace operations yet.
o  Send the second part of CRIU patches (which are
done, but need some little rework for above APIs).

After this lefts a labour to drop compatible flag in
the kernel. So other patches for CRIU will not be
needed, only work on kernel side. While it's not
done, applications will be restored as 32-bit, but
will lack TIF_IA32 flag. That means that till kernel
version, where flag will be finally removed
(on current master, i.e.), the difference between
checkpointed and restored application will be
visible on uprobes/intel lbr/perf tracing and other
kernel parts, that rely on this flag yet.

-- 
Regards,
Dmitry Safonov