From: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>
To: miklos@szeredi.hu
Cc: avagin@openvz.org, ptikhomirov@virtuozzo.com,
khorenko@virtuozzo.com, vvs@virtuozzo.com, ktkhai@virtuozzo.com,
Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>,
linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] overlayfs: C/R enhancements
Date: Thu, 4 Jun 2020 19:11:31 +0300 [thread overview]
Message-ID: <20200604161133.20949-1-alexander.mikhalitsyn@virtuozzo.com> (raw)
This patchset aimed to make C/R of overlayfs mounts with CRIU possible.
We introduce two new overlayfs module options -- dyn_path_opts and
mnt_id_path_opts. If enabled this options allows to see real *full* paths
in lowerdir, workdir, upperdir options, and also mnt_ids for corresponding
paths.
This changes should not break anything because for showing mnt_ids we simply
introduce new show-time mount options. And for paths we simply *always*
provide *full paths* instead of relative path on mountinfo.
BEFORE
overlay on /var/lib/docker/overlay2/XYZ/merged type overlay (rw,relatime,
lowerdir=/var/lib/docker/overlay2/XYZ-init/diff:/var/lib/docker/overlay2/
ABC/diff,upperdir=/var/lib/docker/overlay2/XYZ/diff,workdir=/var/lib/docker
/overlay2/XYZ/work)
none on /sys type sysfs (rw,relatime)
AFTER
overlay on /var/lib/docker/overlay2/XYZ/merged type overlay (rw,relatime,
lowerdir=/var/lib/docker/overlay2/XYZ-init/diff:/var/lib/docker/overlay2/
ABC/diff,upperdir=/var/lib/docker/overlay2/XYZ/diff,workdir=/var/lib/docker
/overlay2/XYZ/work,lowerdir_mnt_id=175:175,upperdir_mnt_id=175)
none on /sys type sysfs (rw,relatime)
Alexander Mikhalitsyn (2):
overlayfs: add dynamic path resolving in mount options
overlayfs: add mnt_id paths options
fs/overlayfs/Kconfig | 57 ++++++++++++++++++++++
fs/overlayfs/overlayfs.h | 7 +++
fs/overlayfs/ovl_entry.h | 6 ++-
fs/overlayfs/super.c | 103 ++++++++++++++++++++++++---------------
fs/overlayfs/util.c | 42 ++++++++++++++++
5 files changed, 174 insertions(+), 41 deletions(-)
--
2.17.1
next reply other threads:[~2020-06-04 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 16:11 Alexander Mikhalitsyn [this message]
2020-06-04 16:11 ` [PATCH 1/2] overlayfs: add dynamic path resolving in mount options Alexander Mikhalitsyn
2020-06-04 16:11 ` [PATCH 2/2] overlayfs: add mnt_id paths options Alexander Mikhalitsyn
2020-06-04 18:04 ` [PATCH 0/2] overlayfs: C/R enhancements Amir Goldstein
2020-06-04 21:34 ` Alexander Mikhalitsyn
2020-06-05 2:35 ` Amir Goldstein
2020-06-05 8:41 ` Pavel Tikhomirov
2020-06-05 10:21 ` Amir Goldstein
2020-06-05 12:44 ` Alexander Mikhalitsyn
2020-06-05 14:36 ` Amir Goldstein
2020-06-05 14:56 ` Alexander Mikhalitsyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200604161133.20949-1-alexander.mikhalitsyn@virtuozzo.com \
--to=alexander.mikhalitsyn@virtuozzo.com \
--cc=avagin@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ptikhomirov@virtuozzo.com \
--cc=vvs@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).