From: Miklos Szeredi <miklos@szeredi.hu>
To: viro@ZenIV.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
apw@canonical.com, nbd@openwrt.org, neilb@suse.de,
hramrach@centrum.cz, Miklos Szeredi <mszeredi@suse.cz>
Subject: [PATCH 3/6] vfs: introduce clone_private_mount()
Date: Mon, 18 Apr 2011 18:00:37 +0200 [thread overview]
Message-ID: <1303142440-26328-4-git-send-email-miklos@szeredi.hu> (raw)
In-Reply-To: <1303142440-26328-1-git-send-email-miklos@szeredi.hu>
From: Miklos Szeredi <mszeredi@suse.cz>
Overlayfs needs a private clone of the mount, so create a function for
this and export to modules.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
---
fs/namespace.c | 17 +++++++++++++++++
include/linux/mount.h | 3 +++
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index d99bcf5..4bcc60e 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -1494,6 +1494,23 @@ void drop_collected_mounts(struct vfsmount *mnt)
release_mounts(&umount_list);
}
+struct vfsmount *clone_private_mount(struct path *path)
+{
+ struct vfsmount *mnt;
+
+ if (IS_MNT_UNBINDABLE(path->mnt))
+ return ERR_PTR(-EINVAL);
+
+ down_read(&namespace_sem);
+ mnt = clone_mnt(path->mnt, path->dentry, CL_PRIVATE);
+ up_read(&namespace_sem);
+ if (!mnt)
+ return ERR_PTR(-ENOMEM);
+
+ return mnt;
+}
+EXPORT_SYMBOL_GPL(clone_private_mount);
+
int iterate_mounts(int (*f)(struct vfsmount *, void *), void *arg,
struct vfsmount *root)
{
diff --git a/include/linux/mount.h b/include/linux/mount.h
index 604f122..44e9bf4 100644
--- a/include/linux/mount.h
+++ b/include/linux/mount.h
@@ -100,6 +100,9 @@ extern void mnt_pin(struct vfsmount *mnt);
extern void mnt_unpin(struct vfsmount *mnt);
extern int __mnt_is_readonly(struct vfsmount *mnt);
+struct path;
+extern struct vfsmount *clone_private_mount(struct path *path);
+
extern struct vfsmount *do_kern_mount(const char *fstype, int flags,
const char *name, void *data);
--
1.7.1
next prev parent reply other threads:[~2011-04-18 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 16:00 [PATCH 0/6] overlay filesystem Miklos Szeredi
2011-04-18 16:00 ` [PATCH 1/6] vfs: add i_op->open() Miklos Szeredi
2011-04-18 16:00 ` [PATCH 2/6] vfs: export do_splice_direct() to modules Miklos Szeredi
2011-04-18 16:00 ` Miklos Szeredi [this message]
2011-04-18 16:00 ` [PATCH 4/6] overlay filesystem Miklos Szeredi
2011-04-18 16:00 ` [PATCH 5/6] overlayfs: add statfs support Miklos Szeredi
2011-04-18 16:00 ` [PATCH 6/6] overlay: overlay filesystem documentation Miklos Szeredi
2011-04-19 3:05 ` J. R. Okajima
2011-04-19 3:58 ` NeilBrown
2011-04-19 4:13 ` J. R. Okajima
2011-04-18 18:19 ` [PATCH 0/6] overlay filesystem Michal Suchanek
2011-04-19 9:39 ` Miklos Szeredi
2011-04-19 9:43 ` [PATCH 1/2] ovl: fix missing include Miklos Szeredi
2011-04-19 9:43 ` [PATCH 2/2] ovl: fix building as a module Miklos Szeredi
2011-05-09 19:14 ` [PATCH 0/6] overlay filesystem Michal Suchanek
2011-05-10 16:30 ` 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=1303142440-26328-4-git-send-email-miklos@szeredi.hu \
--to=miklos@szeredi.hu \
--cc=apw@canonical.com \
--cc=hramrach@centrum.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=nbd@openwrt.org \
--cc=neilb@suse.de \
--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).