From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 0/3] Overlayfs mkdir related fixes
Date: Sat, 12 May 2018 12:17:08 +0300 [thread overview]
Message-ID: <1526116631-24186-1-git-send-email-amir73il@gmail.com> (raw)
Miklos,
This series supersedes the patch
"ovl: be more prudent when instantiating a new dentry",
which is based on overlayfs-rorw.
The series is based and tested on top of a merge of overlayfs-rorw and
Al's fixes branch and should apply pretty cleanly to fixes branch.
BTW, I noticed there is a small conflict between Al's for-next and
your dedupe-cleanup branch, so you might want to rebase that.
Thanks,
Amir.
Changes since v1:
- Rebase on top of Al's fixes branch
- Use d_instantiate_new() helper
- Add re-factoring + Al's vfs_mkdir() safely patch
Al Viro (1):
ovl: make ovl_create_real() cope with vfs_mkdir() safely
Amir Goldstein (2):
ovl: use d_instantiate_new() to instantiate a new dentry
ovl: create helper ovl_create_temp()
fs/overlayfs/copy_up.c | 27 ++++----------
fs/overlayfs/dir.c | 96 +++++++++++++++++++++++++++++++++---------------
fs/overlayfs/inode.c | 6 +++
fs/overlayfs/overlayfs.h | 12 +++++-
fs/overlayfs/super.c | 2 +-
5 files changed, 90 insertions(+), 53 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-12 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 9:17 Amir Goldstein [this message]
2018-05-12 9:17 ` [PATCH v2 1/3] ovl: use d_instantiate_new() to instantiate a new dentry Amir Goldstein
2018-05-12 9:41 ` Amir Goldstein
2018-05-14 20:30 ` Vivek Goyal
2018-05-15 5:20 ` Amir Goldstein
2018-05-12 9:17 ` [PATCH v2 2/3] ovl: create helper ovl_create_temp() Amir Goldstein
2018-05-12 9:17 ` [PATCH v2 3/3] ovl: make ovl_create_real() cope with vfs_mkdir() safely 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=1526116631-24186-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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).