- 06 Aug, 2014 31 commits
-
-
Cyrill Gorcunov authored
Signed-off-by:
Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by:
Pavel Emelyanov <xemul@parallels.com>
-
Cyrill Gorcunov authored
Signed-off-by:
-
Cyrill Gorcunov authored
Signed-off-by:
-
Cyrill Gorcunov authored
Will need it to carry timerfd entries. Signed-off-by:
-
Christopher Covington authored
This is required to support checkpoint and restore of timers that notify via file descriptors on ARM and AArch64. Signed-off-by:
Christopher Covington <cov@codeaurora.org> Signed-off-by:
-
Cyrill Gorcunov authored
Signed-off-by:
-
Andrey Vagin authored
v2: change an author field in a test Signed-off-by:
Andrey Vagin <avagin@openvz.org> Signed-off-by:
-
Andrey Vagin authored
Check that files opened before switching to new mount namespace remain in it after restore. Right now this is not so :( Andrey is fixing the issue. Christopher, can you check whether the ns_child's call to system() works in your minimal set-ups (it launches cat and awk). If not, then I should rewrite this routine in pure C. The first version was written by Pavel (xemul@). v2: don't use test_init_ns don't call awk and cat Signed-off-by: -
Andrey Vagin authored
v2: add a comment before mntns_get_root_by_mnt_id(-1); Signed-off-by:
-
Andrey Vagin authored
Here is a problem with ghost files. Links are created on restore, but they can't be created on any mount point, because a mount point can be non-root bind-mount of another one. So we need to find the root mount and create all links there. v2: clean up v3: add optimization for the case when both links on the same mount point. v4: don't look up mount points by mnt_id in a second time. Signed-off-by:
-
Andrey Vagin authored
On restore we add a temporary root to a mount point path. It's convinient for restoring mount namespaces, but real paths are used for restoring link-remap files. v2: replace the offset field on a char * field Signed-off-by:
-
Andrey Vagin authored
The m->bind will be used to get the "lowest" mount. A mount is called "lowest" in the chain of bind-mounts when its m->bind is NULL. I.e. -- it's the mount of the root dir of an FS, all the others are bind-mounted from it. The propagate_siblings() is called for each new mount and sets the bind field for others. A part of these other mounts can be already mounted. Signed-off-by:
-
Christopher Covington authored
This modifies the x86 VDSO code to work on AArch64. Signed-off-by:
-
Christopher Covington authored
While it duplicates hundreds of lines of code, this is the short term strategy Cyrill and I have agreed to for supporting VDSOs across multiple architectures [1]. With better understanding of where things differ per-architecture, or even improved consolidation in the kernel, we can hopefully move to a more shared implementation in the future. 1. http://lists.openvz.org/pipermail/criu/2014-August/015218.htmlAcked-by:
-
Ruslan Kuprieiev authored
As it was reported, some systems don't use /etc/passwd. On such systems getpwuid fails with undefined errno(see getpwuid(3)) not allowing criu to restrict ids with user additional groups. Luckily, on such systems criu is run as root, so we can just skip obtaining additional groups, as they don't matter for root. Reported-by:
Ruslan Kuprieiev <kupruser@gmail.com> Tested-by:
-
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
This makes the API simpler. Signed-off-by: -
Pavel Emelyanov authored
This makes the API simpler. Signed-off-by: -
Ruslan Kuprieiev authored
This test creates 2 users to check how secure is using criu with setuid bit set. Signed-off-by:
-
Ruslan Kuprieiev authored
Currently check_ids is used to check uids only. So lets rename it and drop crid argument, as we can use cr_uid directly. Signed-off-by:
-
Ruslan Kuprieiev authored
Currently, we only check if process gids match primary gid of user. But process and user have additional groups too. So lets: 1) check that process rgid,egid and sgid are in the user's grouplist. 2) on restore check that user has all groups from the images. Signed-off-by: -
Cyrill Gorcunov authored
Otherwise we might take a look on last vma from previous cycle not running vdso analisys at all. Signed-off-by:
-
Cyrill Gorcunov authored
Occasionally I ruined the ability to do a in-place remap for pre 3.16 kernels. Bring it back. CID 1230182: Logically dead code (DEADCODE) Signed-off-by:
-
Cyrill Gorcunov authored
No need for second if() statement, merge everything in previous one. Signed-off-by:
-
Pavel Emelyanov authored
... free the pointer itself :) 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: -
Ruslan Kuprieiev authored
Signed-off-by:
-
Ruslan Kuprieiev authored
When performing "make clean" rpc_pb2.pyc should be deleted as well. Signed-off-by:
-
- 05 Aug, 2014 6 commits
-
-
Andrey Vagin authored
openat() is used to open files, so absolute pathes can't be used v2: change the comment Signed-off-by:
-
Andrey Vagin authored
Here is a bug now. A path for devices and directories should be generated with a specified root. Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
For that mnt namespaces should be dumped after files. v2: rework enumeration of namespaces in dump_mnt_namespaces() Signed-off-by:
-
Andrey Vagin authored
Currently collect_shared is executed for each mount namespace separately, so we miss the dependencies between namespaces. For example, we have two namespaces, the first one contains a tmpfs mount and the second one contains a non-root bind-mount of this tmpfs. Without this patch this example can't be dumped. On restore mnt_build_tree() is called for all namespaces at once, thus this bug doesn't exist there. Signed-off-by:
-
Andrey Vagin authored
$ bash test/zdtm.sh -i 0 '\(ns/static/env00\|static/pty03\|static/mountpoints\)' ... ==================================== ERROR ==================================== Test: zdtm/live/static/mountpoints, Namespace: Output file: /root/git/1/criu/test/zdtm/live/static/mountpoints.out ------------------------------------------------------------------------------ 00:53:03.267: 26935: FAIL: mountpoints.c:139: Can't umount all the filesystems (errno = 16 (Device or resource busy)) ------------------------------------- END ------------------------------------- ================================= ERROR OVER ================================= Fixes: 0198590c (zdtm: Factor out starting the test via Makefule) Signed-off-by:
-
- 04 Aug, 2014 3 commits
-
-
Cyrill Gorcunov authored
In worst case we might be tryin to proxify vdso zone when vvar only is remmaped but vdso itself is not yet (left and right zones shifting). Thus vdso_proxify will complain that vdso is not yet mapped refusing to restore. Thus wait until everything is re-mapped then call for proxification helper. Reported: Mr. Jenkins Signed-off-by:
Andrew Vagin <avagin@parallels.com> Signed-off-by:
-
Cyrill Gorcunov authored
In latest linux-next the vdso zone is placed _after_ vvar zone so eventually we need to handle any combination of the following cases - no vvar zone - vvar before vdso - vvar after vdso Here we address all them. Signed-off-by:
-
Cyrill Gorcunov authored
Since we might have a several vDSO zones lets hide handling in arch-specific routines. Signed-off-by:
-
