From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-unionfs@vger.kernel.org
Subject: [PATCH v7 0/8] Overlayfs: constant st_ino/d_ino for non-samefs
Date: Thu, 2 Nov 2017 22:38:03 +0200 [thread overview]
Message-ID: <1509655091-13630-1-git-send-email-amir73il@gmail.com> (raw)
Miklos,
This version is cleaner and better tested.
I have a WIP for xfstest for the new cases, will clean it up and post
it later.
Changes since v6:
- Reorganize d_ino patches to: 1. merge dir cache and 2. impure dir cache
- Explain better why we need to return pseudo st_dev for lower
- Fix crash on building impure cache for pure lower
- Reset cache on change of dir from is_real to !is_real
Thanks,
Amir.
[1] https://github.com/amir73il/linux/commits/ovl-nonsamefs-v7
Amir Goldstein (5):
ovl: move include of ovl_entry.h into overlayfs.h
ovl: relax same fs constraint for constant st_ino
ovl: recalc d_ino for dir cache in non-samefs case
ovl: update cache version of impure parent on rename
ovl: ovl_iterate_real() for all pure upper/lower in non-samefs case
Chandan Rajendra (3):
ovl: re-structure overlay lower layers in-memory
ovl: allocate anonymous devs for lowerdirs
ovl: return anonymous st_dev for lower inodes
fs/overlayfs/copy_up.c | 1 -
fs/overlayfs/dir.c | 16 ++++++----
fs/overlayfs/inode.c | 51 +++++++++++++++++++++---------
fs/overlayfs/namei.c | 53 ++++++++++++++++++-------------
fs/overlayfs/overlayfs.h | 7 +++--
fs/overlayfs/ovl_entry.h | 14 +++++++--
fs/overlayfs/readdir.c | 64 +++++++++++++++++++++++++++-----------
fs/overlayfs/super.c | 81 ++++++++++++++++++++++++++++++------------------
fs/overlayfs/util.c | 17 +++++++---
9 files changed, 202 insertions(+), 102 deletions(-)
--
2.7.4
next reply other threads:[~2017-11-02 20:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 20:38 Amir Goldstein [this message]
2017-11-02 20:38 ` [PATCH v7 1/8] ovl: move include of ovl_entry.h into overlayfs.h Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 2/8] ovl: re-structure overlay lower layers in-memory Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 3/8] ovl: allocate anonymous devs for lowerdirs Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 4/8] ovl: return anonymous st_dev for lower inodes Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 5/8] ovl: relax same fs constraint for constant st_ino Amir Goldstein
2017-11-06 20:43 ` Vivek Goyal
2017-11-06 21:06 ` Amir Goldstein
2017-11-06 21:10 ` Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 6/8] ovl: recalc d_ino for dir cache in non-samefs case Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 7/8] ovl: update cache version of impure parent on rename Amir Goldstein
2017-11-06 9:17 ` Miklos Szeredi
2017-11-06 10:06 ` Amir Goldstein
2017-11-06 10:39 ` Miklos Szeredi
2017-11-06 10:59 ` Amir Goldstein
2017-11-02 20:38 ` [PATCH v7 8/8] ovl: ovl_iterate_real() for all pure upper/lower in non-samefs case Amir Goldstein
2017-11-06 9:35 ` Miklos Szeredi
2017-11-06 10:08 ` Amir Goldstein
2017-11-06 10:54 ` Amir Goldstein
2017-11-06 11:45 ` Amir Goldstein
2017-11-06 13:57 ` Miklos Szeredi
2017-11-06 14:30 ` Amir Goldstein
2017-11-06 14:52 ` Miklos Szeredi
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=1509655091-13630-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=vgoyal@redhat.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).