public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: [PATCH v2 0/3] Enable new features for nested overlayfs setups
Date: Thu,  8 Nov 2018 13:49:39 +0200	[thread overview]
Message-ID: <20181108114942.32531-1-amir73il@gmail.com> (raw)

Miklos,

Based on your feedback on v1 [1], following patches implement
"nested xino", where "nested" doesn't have to be overlayfs over
overlayfs. It can be overlayfs over another fs that publishes
ino domain information, or another stacked fs aware of ino
domains over overlayfs.

Series is available on my ovl-nested branch [2].
xfstests are also available on my github [3].
Note that the tests in group "overlay/exportfs.nested" already pass
on current master.

The test group "overlay/union" uses the xfstests harness to run
various unionmount-testsuite setups (e.g. samefs, non-samefs,
non-samefs with some layers on same fs). This test group requires
the symlink src/unionmount-testsuite to run the test suite.

Thanks,
Amir.

Changes since v1:
- "relax requirement for non null uuid" already merged
- Teach vfs about inode number domains
- Don't special case overlayfs as a lower fs

[1] https://marc.info/?l=linux-unionfs&m=154039437114960&w=2
[2] https://github.com/amir73il/linux/commits/ovl-nested
[3] https://github.com/amir73il/xfstests/commits/ovl-nested

Amir Goldstein (3):
  vfs: introduce the concept of inode number domains
  ovl: limit xino for some nested overlay cases
  ovl: relax xino for some nested overlay cases

 fs/overlayfs/ovl_entry.h |   7 +-
 fs/overlayfs/super.c     | 200 ++++++++++++++++++++++++++++++---------
 fs/overlayfs/util.c      |   2 +-
 fs/super.c               |   2 +
 include/linux/fs.h       |  18 +++-
 5 files changed, 179 insertions(+), 50 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-11-08 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 11:49 Amir Goldstein [this message]
2018-11-08 11:49 ` [PATCH v2 1/3] vfs: introduce the concept of inode number domains Amir Goldstein
2018-11-08 11:49 ` [PATCH v2 2/3] ovl: limit xino for some nested overlay cases Amir Goldstein
2018-11-08 11:49 ` [PATCH v2 3/3] ovl: relax " Amir Goldstein
2019-01-11  6:37 ` [PATCH v2 0/3] Enable new features for nested overlayfs setups 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=20181108114942.32531-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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