[CRIU] [PATCH] arm: mark the "[vectors]" vma as VMA_AREA_VSYSCALL
Andrey Vagin
avagin at openvz.org
Mon Sep 23 09:48:31 EDT 2013
This vma looks like VSYSCALL on x86. We don't need to dump and restore it.
Currently this vma is dumped and restored as a private vma, but it is not
remmaped in a correct place:
Restore
--- dump/pipe00/6392/1/dump.maps 2013-09-23 12:49:19.436816192 +0000
+++ dump/pipe00/6392/1/restore.maps 2013-09-23 12:49:20.276766356 +0000
@@ -6,5 +6,6 @@ e05000-e26000
4009d000-4009f000
400a0000-400aa000
400b8000-401e7000
+b6d6f000-b6d70000
be838000-be859000
ffff0000-ffff1000
ERROR: Sets of mappings differ:
Signed-off-by: Andrey Vagin <avagin at openvz.org>
---
proc_parse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/proc_parse.c b/proc_parse.c
index 1afa29c..d7add4e 100644
--- a/proc_parse.c
+++ b/proc_parse.c
@@ -281,7 +281,7 @@ int parse_smaps(pid_t pid, struct vm_area_list *vma_area_list, bool use_map_file
if (vma_area->vma.status != 0) {
continue;
- } else if (strstr(buf, "[vsyscall]")) {
+ } else if (strstr(buf, "[vsyscall]") || strstr(buf, "[vectors]")) {
vma_area->vma.status |= VMA_AREA_VSYSCALL;
} else if (strstr(buf, "[vdso]")) {
vma_area->vma.status |= VMA_AREA_REGULAR;
--
1.8.3.1
More information about the CRIU
mailing list