From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: zhangyi <yi.zhang@huawei.com>, linux-unionfs@vger.kernel.org
Subject: [PATCH v6 0/3] Overlayfs fixes for exposed whiteouts
Date: Tue, 31 Oct 2017 23:45:47 +0200 [thread overview]
Message-ID: <1509486350-21362-1-git-send-email-amir73il@gmail.com> (raw)
Miklos,
Let's call my previous version v5 (Zhangyi's last post was v4).
Changes since v5:
- Split ovl_check_empty_and_clear() changes from bug fix patch
- Cache "origin" xattr of non-merge dir in inode flag OVL_WHITEOUTS
(OVL_ORIGIN would have been too confusing)
- Replace layer idx with is_upper boolean
I tested these changes with upstream xfstest overlay/031 by Zhangyi.
Pushed to ovl-whiteouts branch [1] and rebased the non-samefs patches
on top of it [2].
Thanks,
Amir.
[1] https://github.com/amir73il/linux/commits/ovl-whiteouts
[1] https://github.com/amir73il/linux/commits/overlayfs-devel
Amir Goldstein (3):
ovl: no direct iteration for dir with origin xattr
ovl: simplify ovl_check_empty_and_clear()
ovl: fix rmdir problem on non-merge dir with origin xattr
fs/overlayfs/dir.c | 18 ++++++++++------
fs/overlayfs/inode.c | 5 +++++
fs/overlayfs/overlayfs.h | 4 ++++
fs/overlayfs/readdir.c | 56 ++++++++++++++++++++++++++++++++++++++----------
fs/overlayfs/util.c | 13 +++++++++++
5 files changed, 79 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-31 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 21:45 Amir Goldstein [this message]
2017-10-31 21:45 ` [PATCH v6 1/3] ovl: no direct iteration for dir with origin xattr Amir Goldstein
2017-10-31 21:45 ` [PATCH v6 2/3] ovl: simplify ovl_check_empty_and_clear() Amir Goldstein
2017-10-31 21:45 ` [PATCH v6 3/3] ovl: fix rmdir problem on non-merge dir with origin xattr Amir Goldstein
2017-11-01 3:12 ` [PATCH v6 0/3] Overlayfs fixes for exposed whiteouts zhangyi (F)
2017-11-01 6:08 ` 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=1509486350-21362-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.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).