- 30 Oct, 2013 1 commit
-
-
Cyrill Gorcunov authored
In case if we need to use vdso proxy the memory area which holds restorer also has a place for vdso proxy code itself, so on final pass we should not unmap it, otherwise any call to vdso function will cause sigsegv. IOW, the memory before final "cleanup" pass of restorer might look as +-----------+---------+ +-------------+------+ | bootstrap | rt-vdso | ... | application | vdso | +-----------+---------+ +-------------+------+ ^ | `-------------------------+ and we have redirected "vdso" code to jump to "rt-vdso". After final pass the memory must look as +---------+ +-------------+------+ | rt-vdso | ... | application | vdso | +---------+ +-------------+------+ ^ | `-------------------------+ I noticed this problem during container migration testing, the container itself was suspended on 2.6.32 OpenVZ kernel with apache running inside, and any attempt to connect to apache caused apache to crash. Signed-off-by:Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by:
Pavel Emelyanov <xemul@parallels.com>
-
- 29 Oct, 2013 6 commits
-
-
Pavel Emelyanov authored
The ctl->sig_blocked in this place is the same as sigframe's one, as ctl's one was copied into sigframe's few steps before. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by:
-
- 28 Oct, 2013 1 commit
-
-
Andrey Vagin authored
If parasite exited unexpectedly, CRIU gets SIGCHLD and handles it. In sigchld handler we need to wait any child process. Currently criu waits neighbours in its group, but a dumped processes is in another group usually. Here is a typo. Signed-off-by:
Andrey Vagin <avagin@openvz.org> Signed-off-by:
-
- 18 Oct, 2013 1 commit
-
-
Pavel Emelyanov authored
As planned, this was bugfix-mainly release. However, some new features were added. Looking forward the v1.0 release :) Signed-off-by:
-
- 17 Oct, 2013 2 commits
-
-
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
There can be a more sophisticated security policy, but right now generic non-root user doesn't have any bits in there, so requiring them to be zero is a sane starting point. Signed-off-by:
-
- 15 Oct, 2013 12 commits
-
-
Pavel Emelyanov authored
There's ... a number of places where we want to do something with /proc/self/fd/%d path. Each time we guess buffer size that is enough for this. Make standard constant for this and save some space on stack and drop args for some functions. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
CRIU puts wd-s for one inotify in one row (one after another), so when collecting next wd, we can find the ify to attach them to faster. Signed-off-by: -
Pavel Emelyanov authored
The inotify_add_watch generates wd-s one-by one. We cannot request for one, thus we call this syscall till the required wd is generated. Thus, if we want to restore several wd-s for an inotify, we have to put them in ascending order. Otherwise we may restore watch with higher wd earlier and will thus not be able to generate the lower wd in a reasonable time. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
This can be broken image, need to handle this error gracefully. Signed-off-by: -
Pavel Emelyanov authored
Handle the simplest (remap) case early. This makes code simpler and reduces one level of indent. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by:
-
- 14 Oct, 2013 3 commits
-
-
Cyrill Gorcunov authored
Convenient for debug. | (00.005999) 3857: fsnotify: Restore inotify watch for 0x00800002:0x0000000000000002 (via /proc/self/fd/5 -> /) | (00.005999) 3857: fsnotify: Restore inotify watch for 0x00800002:0x0000000000083a93 (via /home/criu/test/zdtm/live/static/inotify-removed (deleted).cr.1.ghost) Signed-off-by:
-
Ruslan Kuprieiev authored
Hi! Added "has_log_level = true" to test.c, so "log_level = 4" would have effect. Also added log_level to test.py, for symmetry with test.c. Signed-off-by:
Ruslan Kuprieiev <kupruser@gmail.com> Signed-off-by:
-
Cyrill Gorcunov authored
Otherwise | Error (proc_parse.c:227): Can't parse: 555555554000-555555577000 r-xp 00000000 b6:d2f61 133545 /sbin/init Signed-off-by:
-
- 11 Oct, 2013 7 commits
-
-
Pavel Emelyanov authored
Signed-off-by: -
Cyrill Gorcunov authored
Igor reported the following file lock | (00.003139) lockinfo: 4:POSIX ADVISORY WRITE 46567 b6:5f0b1:524702 0 EOF | (00.003154) lockinfo: 5:POSIX ADVISORY WRITE 46559 b6:5f0b1:524661 0 EOF | (00.003172) lockinfo: 6:POSIX ADVISORY WRITE 46543 b6:5f0b1:524326 0 0 | (00.003188) lockinfo: 7:POSIX ADVISORY WRITE 46543 b6:5f0b1:524367 0 EOF where device maj number is pretty big and parsing failed. Fix it removing field width. Reported-by:
Igor Sukhih <igor@parallels.com> Signed-off-by:
-
Pavel Emelyanov authored
Logs are put into dedicated logfd, cwd is not used as well. Signed-off-by: -
Pavel Emelyanov authored
This is where such stuff is typically placed. Signed-off-by: -
Cyrill Gorcunov authored
In case if we hit error returned from syscall, better to print error code for easier understanding of the protblem. Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
This can hppen if criu is run in container. Reported-by:
Frederico Araujo <araujof@gmail.com> Signed-off-by:
-
- 10 Oct, 2013 7 commits
-
-
Cyrill Gorcunov authored
To get more detailed error desciption. Also print watchdog number if it exceed expected, for better error output. Signed-off-by:
-
Cyrill Gorcunov authored
It's a way more easier to read. Signed-off-by:
-
Cyrill Gorcunov authored
Signed-off-by:
-
Jamie Liu authored
Signed-off-by:
Jamie Liu <jamieliu@google.com> Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by: -
Cyrill Gorcunov authored
Signed-off-by:
-
Cyrill Gorcunov authored
Signed-off-by:
-
