- 22 Apr, 2014 21 commits
-
-
Pavel Emelyanov authored
Acked-by:
Andrew Vagin <avagin@parallels.com> Signed-off-by:
Pavel Emelyanov <xemul@parallels.com>
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Helper for simpler next patch. Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
This is a helper for the next patch. Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Pavel Emelyanov authored
Acked-by:
-
Cyrill Gorcunov authored
In the early draft of kcmp syscall it has been returning [-1|0|1] values but finally [0|1|2] were merged into the kernel, but I forgot to update the criu code. The good thing is that because we're using rbtree the kcmp results are still sorted and tree is balanced but sometime we may take a wrong branch generating new ID even if the object is present in the tree which eventually may lead to dump faulure. Reported-by:
Deyan Doychev <deyan@1h.com> Signed-off-by:
Cyrill Gorcunov <gorcunov@openvz.org> Acked-by:
-
- 21 Apr, 2014 19 commits
-
-
Andrey Vagin authored
When we don't know mnt_id, we don't know to which namespace a file belongs. Signed-off-by:
Andrey Vagin <avagin@openvz.org> Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
This patch removes the global mntinfo_tree and collect_mount_info where it was constructed. The mntinfo list is filled from dump_mnt_ns, rst_collect_local_mntns, collect_mnt_namespaces and read_mnt_ns_img. A mountinfo entry contains a reference on a proper ns_id entry, so we cau use mnt_id to look up a proper mount namespace. v2: remove trash after rebasing. Signed-off-by:
-
Andrey Vagin authored
On restore all namespaces are restored as one tree and a pointer on the root of this tree will be set on each namespace. Below you can find a call trace, where it's used: Signed-off-by:
-
Andrey Vagin authored
It's a typo fix. Signed-off-by:
-
Andrey Vagin authored
Kernels before 3.15 doesn't show mnt_id and mnt_id isn't saved in images, if mntns isn't dumped. Signed-off-by:
-
Andrey Vagin authored
They are used for collecting unix sockets Signed-off-by:
-
Andrey Vagin authored
We are going to dump nested mount namespaces, so we move the mountinfo list on the namespace structure. Signed-off-by:
-
Andrey Vagin authored
On restore all mount namespaces are restored in the root mntns and sub-namecpeaces are restored in temorary places. This function allows to get paths to these places. It will be used in open_remap_ghost(), because it's called in the root task, when other tasks are not forked yet. Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
We are going to support nested mount namespaces, file descriptors can be from different namespaces, so a namespace root must be updated for each of them. Signed-off-by:
-
Andrey Vagin authored
We want to look up mntns by mnt_id. Signed-off-by:
-
Andrey Vagin authored
It's required for restoring in the current mntns. Signed-off-by:
-
Andrey Vagin authored
We are going to support nested mntns, so the global mntinfo_tree variable are useless and information about tree should be connected to a proper namespace. But when we don't dump mntns, we need to collect mounts for the current mntns. Signed-off-by:
-
Andrey Vagin authored
It will fill mntinfo list and this is internal logic of mount.c Signed-off-by:
-
Andrey Vagin authored
We are going to support nested mount namespaces and each NS has own tree. The mount tree is used for checking that a file is reachable. Signed-off-by:
-
Andrey Vagin authored
We are going to support nested mount namespaces, so files can be opened from more than one namespace and a root must be collect for each file. Signed-off-by:
-
