mirror of
https://github.com/checkpoint-restore/criu
synced 2025-08-31 06:15:24 +00:00
introduce --skip-mnt cli option
Which obviously can be used to "ignore" the mounts we do not want or need to dump. The user should know what he does. Note: this patch changes parse_mountinfo() to check should_skip_mount(). This is because imo we want to filter out the unwanted mounts asap, af if they do not exist. This increases the chances the dumping will fail if something else depends on this mount. Say, another mountpoint or an opened file. Perhaps it makes sense to teach should_skip_mount() to use fnmatch() and/or look at the optional "(fs|mnt)=" prefix to skip by fsname too. To me it would be better to force the user of this option to understand what it does. Say, if "dump" fails because the child mount can't find the skipped parent, he should add another --skip-mnt option or do not dump. Otherwise, if we do this automagically the user can probably be surpised, he might even miss the fact that we skip more than he asked. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
This commit is contained in:
committed by
Pavel Emelyanov
parent
9fee3dc817
commit
eb518936d8
@@ -153,6 +153,7 @@ extern void mnt_entry_free(struct mount_info *mi);
|
||||
|
||||
struct vm_area_list;
|
||||
|
||||
extern bool add_skip_mount(const char *mountpoint);
|
||||
extern struct mount_info *parse_mountinfo(pid_t pid, struct ns_id *nsid, bool for_dump);
|
||||
extern int parse_pid_stat(pid_t pid, struct proc_pid_stat *s);
|
||||
extern int parse_smaps(pid_t pid, struct vm_area_list *vma_area_list);
|
||||
|
Reference in New Issue
Block a user