From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-unionfs@vger.kernel.org
Subject: [PATCH v3 0/5] ovl: constant inode numbers (cont.)
Date: Thu, 1 Jun 2017 12:02:54 +0300 [thread overview]
Message-ID: <1496307779-2766-1-git-send-email-amir73il@gmail.com> (raw)
Miklos,
This series covers many of the constant inode number leftovers from v4.12.
Current status is:
- For non-hardlinks, st_ino is constant and consistent with d_ino
- For samefs and for non-dir, st_ino/d_ino is also persistent
- For samefs, st_dev;st_ino is also system-wide unique
The remaining leftovers:
- Constant st_ino/d_ino for hardlinks (WIP by me)
- System-wide unique st_dev;st_ino for non-samefs (WIP by Chandan?)
Tested constant and consistent d_ino with improved xfstest overlay/017,
already upstream, which currently fails only on the hardlink copy up test.
v3:
- Relax same fs contrains from v4.12
- Non "impure" dir optimizations
v2:
- Lookup overlay entry with lookup_one_len_noperm()
v1:
- Resurect Miklos's constant d_ino POC
- Lookup overlay entry with lookup_one_len()
Amir Goldstein (5):
ovl: relax same fs constrain for ovl_check_origin()
ovl: relax same fs constrain for constant st_ino
vfs: factor out lookup_one_len_init()
vfs: add helper lookup_one_len_noperm()
ovl: consistent st_ino/d_ino
fs/namei.c | 117 +++++++++++++++++++++++------------------
fs/overlayfs/inode.c | 32 +++++++-----
fs/overlayfs/namei.c | 50 +++++++++++-------
fs/overlayfs/overlayfs.h | 2 +-
fs/overlayfs/readdir.c | 133 ++++++++++++++++++++++++++++++++++++++++++++---
include/linux/namei.h | 1 +
6 files changed, 244 insertions(+), 91 deletions(-)
--
2.7.4
next reply other threads:[~2017-06-01 9:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 9:02 Amir Goldstein [this message]
2017-06-01 9:02 ` [PATCH v3 1/5] ovl: relax same fs constrain for ovl_check_origin() Amir Goldstein
2017-06-01 9:02 ` [PATCH v3 2/5] ovl: relax same fs constrain for constant st_ino Amir Goldstein
2017-06-01 12:30 ` Chandan Rajendra
2017-06-01 13:32 ` Amir Goldstein
2017-06-01 19:55 ` Miklos Szeredi
2017-06-02 6:32 ` Amir Goldstein
2017-06-02 12:27 ` Miklos Szeredi
2017-06-02 13:23 ` Amir Goldstein
2017-06-02 13:26 ` Miklos Szeredi
2017-06-02 13:34 ` Amir Goldstein
2017-06-01 9:02 ` [PATCH v3 3/5] vfs: factor out lookup_one_len_init() Amir Goldstein
2017-06-01 9:02 ` [PATCH v3 4/5] vfs: add helper lookup_one_len_noperm() Amir Goldstein
2017-06-05 12:36 ` Amir Goldstein
2017-06-01 9:02 ` [PATCH v3 5/5] ovl: consistent st_ino/d_ino Amir Goldstein
2017-06-20 21:25 ` Miklos Szeredi
2017-06-21 8:03 ` Amir Goldstein
2017-06-21 8:20 ` Miklos Szeredi
2017-06-21 8:38 ` Miklos Szeredi
2017-06-21 8:45 ` Miklos Szeredi
2017-06-21 8:49 ` Amir Goldstein
2017-06-21 8:53 ` Miklos Szeredi
2017-06-21 9:05 ` Amir Goldstein
2017-06-21 9:20 ` Miklos Szeredi
2017-06-21 9:36 ` Amir Goldstein
2017-06-21 9:38 ` Amir Goldstein
2017-06-21 9:48 ` Miklos Szeredi
2017-06-23 13:56 ` Amir Goldstein
2017-06-30 16:23 ` Chandan Rajendra
2017-06-30 19:01 ` Amir Goldstein
2017-07-27 20:00 ` Miklos Szeredi
2017-07-28 9:25 ` Amir Goldstein
2017-07-29 10:33 ` Amir Goldstein
2017-07-31 10:58 ` Miklos Szeredi
2017-08-16 11:16 ` Amir Goldstein
2017-07-29 11:26 ` Chandan Rajendra
2017-08-03 7:18 ` Chandan Rajendra
2017-08-03 9:53 ` Chandan Rajendra
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=1496307779-2766-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 \
/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