[CRIU] kmem with cgroups with different kernels = hell. kmem with criu also appears to be hell might have solution.

Peter Dolding oiaohm at gmail.com
Fri Feb 15 22:32:56 EST 2013


kmem with cgroups with different kernels issue is that in different
kernels different structs can be different sizes.  So value you set in
kmem option of cgroups to allow program to have enough memory changes
kernel to kernel.   This sux for direct reason.

Criu with kernel memory does not have a nice list to see what an
application has used in kernel memory.

What I am suggesting might be nuts but it also might be the simplest
way long term.

Add  a struct that records applications kernel struct usage.    From
this a tool to do from struct list to kmem be done.

This would allow Criu to see like if an application has taken out
posix timers or any other storage.   This is adptable kernel adds new
structor that links to user-space count list of structs expands by 1.

Secuirty side this could be far more effective than watching sys
calls.  Since this say you are only allowed X amount of stuff.  So a
application that only open 2 files only can open 2 files since it only
have the structs for 2 files.  Kinda makes people life injecting code
harder.

Tell me if I am way off here.

Peter Dolding


More information about the CRIU mailing list