linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
	zhangyi <yi.zhang@huawei.com>,
	linux-unionfs@vger.kernel.org
Subject: [PATCH v5 0/4] Overlayfs: constant st_ino/d_ino for non-samefs
Date: Mon, 30 Oct 2017 22:27:23 +0200	[thread overview]
Message-ID: <1509395247-15180-1-git-send-email-amir73il@gmail.com> (raw)

Miklos,

I rebased and pushed a new version of Chandan's patches to my
overlayfs devel branch [1].

I am posting this for review here as v5, although I lost count on the real
revision number.

Beyond rebase, cleanup and checkpatch warning fixes I made the following
cosmetic modifications since previous version:

1. s/struct ovl_lower_mnt/struct ovl_layer
2. s/struct ovl_lower/struct ovl_path
3. s/ofs->lower_mnt/ofs->lower_layers
4. ovl_find_layer() mini helper for ovl_lookup()
5. split cleanup patch of include ovl_entry.h

The cosmetic changes make the struct member variables names .layer and
.lower_layers consistent with their type (struct ovl_layer).
The type name struct ovl_path fits better IMO to the argument list of
ovl_check_origin() which will later be used to check "upper origin"
as well (index=all patches).

I tested these patches with upstream xfstest overlay/041 by Chandan
and with unionmount test './run --ov --verify' that is avialble on my
unionmount devel branch [2].

My overlayfs devel branch [1] contains also the patches by Zhangyi
for not exposing whiteouts when lower dir is gone missing. I tested these
changes with upstream xfstest overlay/031 by Zhangyi.

Please consider the patches from my devel branch [1] for v4.15.

Thanks,
Amir.

[1] https://github.com/amir73il/linux/commits/overlayfs-devel
[2] https://github.com/amir73il/unionmount-testsuite/commits/overlayfs-devel

Amir Goldstein (2):
  ovl: move include of ovl_entry.h into overlayfs.h
  ovl: relax same fs constrain for constant st_ino

Chandan Rajendra (2):
  ovl: allocate anonymous devs for lowerdirs
  ovl: relax same fs constraint for constant d_ino

 fs/overlayfs/copy_up.c   |  1 -
 fs/overlayfs/inode.c     | 51 +++++++++++++++++++++---------
 fs/overlayfs/namei.c     | 53 ++++++++++++++++++-------------
 fs/overlayfs/overlayfs.h |  5 +--
 fs/overlayfs/ovl_entry.h | 14 +++++++--
 fs/overlayfs/readdir.c   | 24 +++++++-------
 fs/overlayfs/super.c     | 81 ++++++++++++++++++++++++++++++------------------
 fs/overlayfs/util.c      |  8 +++--
 8 files changed, 152 insertions(+), 85 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-10-30 20:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 20:27 Amir Goldstein [this message]
2017-10-30 20:27 ` [PATCH v5 1/4] ovl: move include of ovl_entry.h into overlayfs.h Amir Goldstein
2017-10-31 13:14   ` Miklos Szeredi
2017-10-31 13:22     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 2/4] ovl: allocate anonymous devs for lowerdirs Amir Goldstein
2017-10-31 13:43   ` Miklos Szeredi
2017-10-31 13:53     ` Amir Goldstein
2017-10-31 23:01       ` Amir Goldstein
2017-11-01 13:17         ` Chandan Rajendra
2017-11-01 13:34           ` Amir Goldstein
2017-11-01 14:42   ` Vivek Goyal
2017-11-01 15:02     ` Amir Goldstein
2017-11-01 15:47       ` Vivek Goyal
2017-11-01 16:41         ` Amir Goldstein
2017-11-02 12:27           ` Vivek Goyal
2017-11-02 12:47             ` Amir Goldstein
2017-11-02 14:05               ` Vivek Goyal
2017-11-02 14:38                 ` Amir Goldstein
2017-11-01 15:41   ` Vivek Goyal
2017-11-01 16:30     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 3/4] ovl: relax same fs constrain for constant st_ino Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 4/4] ovl: relax same fs constraint for constant d_ino 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=1509395247-15180-1-git-send-email-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=yi.zhang@huawei.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).