I'd be a bit more comfortable if there was some sign that other c/r
developers have reviewed and tested this and have successfully used it
in c/r operation testing?
We've been trying to isolate the c/r-specific functions inside #ifdef
CONFIG_CHECKPOINT_RESTORE, but this patch doesn't do that. I have been
encouraging this isolation so that people who aren't using c/r don't
have to carry the overhead it adds and so that we can more easily hunt
down and remove everything if the entire c/r project doesn't work out
successfully.
This patch modifies the sys_msgrcv() API and so we should update the
manpage for that syscall. Please work with Michael on this.
What does all the compat fiddling actually do? I guess it's needed for
checkpoint and restore of 32-bit userspace on 64-bit kernels? Does c/r
as a whole support that? It should. How well tested is this?