From: Kinglong Mee <kinglongmee@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, NeilBrown <neilb@suse.de>,
Trond Myklebust <trond.myklebust@primarydata.com>,
kinglongmee@gmail.com
Subject: [PATCH 3/6 v10] path: New helpers path_get_pin/path_put_unpin for path,pin
Date: Mon, 7 Sep 2015 22:04:05 +0800 [thread overview]
Message-ID: <55ED9955.2040209@gmail.com> (raw)
In-Reply-To: <55ED9899.9010401@gmail.com>
Two helpers for filesystem pining to vfsmnt, not mntget.
v9, Update base on NeilBrown's new patch
v10, same as v9
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
---
fs/namei.c | 26 ++++++++++++++++++++++++++
include/linux/path.h | 4 ++++
2 files changed, 30 insertions(+)
diff --git a/fs/namei.c b/fs/namei.c
index 29b9279..3a5b0eb 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -492,6 +492,32 @@ void path_put(const struct path *path)
}
EXPORT_SYMBOL(path_put);
+/**
+ * path_get_pin - get a reference to a path's dentry
+ * and pin to path's vfsmnt
+ * @path: path to get the reference to
+ * @p: the fs_pin pin to vfsmnt
+ */
+void path_get_pin(struct path *path, struct fs_pin *p)
+{
+ dget(path->dentry);
+ pin_insert_group(p, path->mnt, NULL);
+}
+EXPORT_SYMBOL(path_get_pin);
+
+/**
+ * path_put_unpin - put a reference to a path's dentry
+ * and remove pin to path's vfsmnt
+ * @path: path to put the reference to
+ * @p: the fs_pin removed from vfsmnt
+ */
+int path_put_unpin(struct path *path, struct fs_pin *p)
+{
+ dput(path->dentry);
+ return pin_remove(p);
+}
+EXPORT_SYMBOL(path_put_unpin);
+
#define EMBEDDED_LEVELS 2
struct nameidata {
struct path path;
diff --git a/include/linux/path.h b/include/linux/path.h
index d137218..40d376a 100644
--- a/include/linux/path.h
+++ b/include/linux/path.h
@@ -3,6 +3,7 @@
struct dentry;
struct vfsmount;
+struct fs_pin;
struct path {
struct vfsmount *mnt;
@@ -12,6 +13,9 @@ struct path {
extern void path_get(const struct path *);
extern void path_put(const struct path *);
+extern void path_get_pin(struct path *, struct fs_pin *);
+extern int path_put_unpin(struct path *, struct fs_pin *);
+
static inline int path_equal(const struct path *path1, const struct path *path2)
{
return path1->mnt == path2->mnt && path1->dentry == path2->dentry;
--
2.4.3
next prev parent reply other threads:[~2015-09-07 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 14:00 [PATCH 0/6 v10] NFSD: Pin to vfsmount for nfsd exports cache Kinglong Mee
2015-09-07 14:04 ` Kinglong Mee [this message]
[not found] ` <55ED9899.9010401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-07 14:02 ` [PATCH 1/6 v10] fs-pin: allow pin_remove() to be called other than from->kill() Kinglong Mee
2015-09-07 14:03 ` [PATCH 2/6 v10] fs_pin: Export functions for specific filesystem Kinglong Mee
2015-09-07 14:04 ` [PATCH 4/6 v10] fs: New helper legitimize_mntget() for getting a legitimize mnt Kinglong Mee
2015-09-07 14:05 ` [PATCH 5/6 v10] sunrpc: New helper cache_delete_entry for deleting cache_head directly Kinglong Mee
2015-09-07 14:06 ` [PATCH 6/6 v10] nfsd: Allows user un-mounting filesystem where nfsd exports base on Kinglong Mee
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=55ED9955.2040209@gmail.com \
--to=kinglongmee@gmail.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@primarydata.com \
--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).