From: Kinglong Mee <kinglongmee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: "linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>,
Trond Myklebust
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
kinglongmee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: [PATCH 2/6 v10] fs_pin: Export functions for specific filesystem
Date: Mon, 7 Sep 2015 22:03:04 +0800 [thread overview]
Message-ID: <55ED9918.4040306@gmail.com> (raw)
In-Reply-To: <55ED9899.9010401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Exports functions for others who want pin to vfsmount,
eg, nfsd's export cache.
These are needed for any module to participate in pinning.
mnt_pin_kill() and group_pin_kill() are just helper-functions for
unmount etc (and are in fs/internal.h) so don't need to be exported.
v10, same as v4
add exporting of pin_kill.
Signed-off-by: Kinglong Mee <kinglongmee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
fs/fs_pin.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/fs_pin.c b/fs/fs_pin.c
index b7954a9..b1a9654 100644
--- a/fs/fs_pin.c
+++ b/fs/fs_pin.c
@@ -33,6 +33,7 @@ int pin_remove(struct fs_pin *pin)
spin_unlock_irq(&pin->wait.lock);
return ret;
}
+EXPORT_SYMBOL(pin_remove);
void pin_insert_group(struct fs_pin *pin, struct vfsmount *m, struct hlist_head *p)
{
@@ -42,11 +43,13 @@ void pin_insert_group(struct fs_pin *pin, struct vfsmount *m, struct hlist_head
hlist_add_head(&pin->m_list, &real_mount(m)->mnt_pins);
spin_unlock(&pin_lock);
}
+EXPORT_SYMBOL(pin_insert_group);
void pin_insert(struct fs_pin *pin, struct vfsmount *m)
{
pin_insert_group(pin, m, &m->mnt_sb->s_pins);
}
+EXPORT_SYMBOL(pin_insert);
void pin_kill(struct fs_pin *p)
{
@@ -88,6 +91,7 @@ void pin_kill(struct fs_pin *p)
}
rcu_read_unlock();
}
+EXPORT_SYMBOL(pin_kill);
void mnt_pin_kill(struct mount *m)
{
--
2.4.3
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-07 14:03 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 ` [PATCH 3/6 v10] path: New helpers path_get_pin/path_put_unpin for path,pin Kinglong Mee
[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 ` Kinglong Mee [this message]
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=55ED9918.4040306@gmail.com \
--to=kinglongmee-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neilb-l3A5Bk7waGM@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
/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).