From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org, "Rafał Miłecki" <zajec5@gmail.com>,
"Ralph Sennhauser" <ralph.sennhauser@gmail.com>
Subject: [PATCH 0/3] Enable new features for more overlayfs setups
Date: Mon, 3 Sep 2018 09:12:08 +0300 [thread overview]
Message-ID: <20180903061211.20830-1-amir73il@gmail.com> (raw)
Miklos,
The following series enables recent overlayfs features for the
case of lower with no uuid and in particular a nested overlay.
Several posts [1] [2] suggest that both squashfs as lower fs
and nested overlay are used by OpenWrt users.
Turns out it is rather easy to enable xino, index and nfs_export
for some common setups.
Persistent and consistent inode numbers for lower squashfs were
tested with unionmount test:
run --ov --squashfs --verify
Tests for xino and NFS export with nested overlay are available
in my xfstests tree [3]. I did not test NFS export with lower squashfs -
leaving that to interesed OpenWrt users. Intereseted party can
use my ovl-nested [4] branch for testing.
I am not sure how many users need these features for nested overlay,
but nested overlay with index is a pre-requisite for multiple overlayfs
snapshots support.
Note that patch [3/3] is an optimization that is not required for
passing the nested exportfs xfstest tests, but could be useful for
real lower (under nested) fs with large file handle sizes.
Thanks,
Amir.
[1] https://lkml.org/lkml/2017/12/13/220
[2] https://www.spinics.net/lists/linux-unionfs/msg01682.html
[3] https://github.com/amir73il/xfstests/commits/ovl-nested
[4] https://github.com/amir73il/linux/commits/ovl-nested
Amir Goldstein (3):
ovl: relax requirement for non null uuid of lower fs
ovl: disable xino for some nested overlay cases
ovl: compact nested ovl_fh
fs/overlayfs/copy_up.c | 20 +++++++++++++++-
fs/overlayfs/export.c | 15 ++++++++++--
fs/overlayfs/namei.c | 34 +++++++++++++++++++--------
fs/overlayfs/overlayfs.h | 16 ++++++++++---
fs/overlayfs/super.c | 50 ++++++++++++++++++++++++++++++++++++----
fs/overlayfs/util.c | 14 ++++++++---
6 files changed, 126 insertions(+), 23 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-03 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 6:12 Amir Goldstein [this message]
2018-09-03 6:12 ` [PATCH 1/3] ovl: relax requirement for non null uuid of lower fs Amir Goldstein
2018-10-24 14:16 ` Miklos Szeredi
2018-10-24 15:29 ` Amir Goldstein
2018-09-03 6:12 ` [PATCH 2/3] ovl: disable xino for some nested overlay cases Amir Goldstein
2018-10-24 14:30 ` Miklos Szeredi
2018-10-24 15:03 ` Amir Goldstein
2018-10-24 15:19 ` Miklos Szeredi
2018-10-24 16:11 ` Amir Goldstein
2018-09-03 6:12 ` [PATCH 3/3] ovl: compact nested ovl_fh Amir Goldstein
2018-10-24 14:34 ` Miklos Szeredi
2018-10-24 17:56 ` Amir Goldstein
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=20180903061211.20830-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ralph.sennhauser@gmail.com \
--cc=zajec5@gmail.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).