Changes

1,089 bytes added ,  16:37, 20 February 2015
no edit summary
Line 7: Line 7:  
! comments
 
! comments
 
|-
 
|-
| kernel/crtools || Make proper "check lock present" API in the kernel || medium || - || Currently we detect where a file lock belongs to by locking the file again with the strickter lock type.
+
| kernel/crtools || Make proper "check lock present" API in the kernel || medium || - || Currently we detect where a file lock belongs to by locking the file again with the alternative lock type and check how kernel reacts on that. This is not nice as it may tune the lock state on a file. Instead we need the "check lock on fd" call in the kernel.
 
|-
 
|-
| kernel/crtools || Put call to mmap into VDSO || easy || Cyrill || Oleg Nesterov suggests not to patch victim areas to get the call to mmap (for [[parasite code]] and args) but to always have one on VDSO.
+
| kernel/crtools || Put call to mmap into VDSO || easy || Cyrill || To put the [[parasite code]] into target process we modify its code to call the <code>mmap()</code> system call (and the unmodify it back) and put the parasite into new area. Oleg Nesterov suggests not to patch victim, but to always have one on VDSO.
 
|-
 
|-
| crtools || [[Integration]] with other projects || hard || - ||
+
| crtools || [[Integration]] with other projects || hard || - || CRIU is not working great by itself. There's alway some specific about what user wants to dump. Integrating CRIU with other projects will make CRIU work at its best.
 
|-
 
|-
| crtools || Restore tasks into fresh new pid namespace || easy || - || A thing to worry about is this new namespace's init task.
+
| crtools || Restore tasks into fresh new pid namespace || easy || - || When we dumped processes, it can be hard to restore it back, if they didn't live in a pid namespace, due to PIDs conflict. It would be nice to have the ability to ask CRIU to create the pid namespace for those guys and restore them there. A thing to worry about is this new namespace's init task.
 
|-
 
|-
| crtools || Rollback tree state || medium || - ||
+
| crtools || Rollback tree state || medium || - || When we checkpointed process tree with -R option (let them run after checkpoint) we might want to return the tasks into checkpointed state on the same machine. Currently this can only be done by killing the processes and restoring them from scratch. If we could ask CRIU to restore the images ''into'' the ready processes that could speed things up, especially if carefully caring about [[memory changes tracking]].
 
|-
 
|-
 
| crtools || AIO with pending events || medium || - ||
 
| crtools || AIO with pending events || medium || - ||