summaryrefslogtreecommitdiff
path: root/include/linux/fs_pin.h
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2014-08-07 16:39:04 +0400
committerAl Viro <viro@zeniv.linux.org.uk>2014-08-07 22:40:08 +0400
commitefb170c22867cdc6f770de441bdefecec6712199 (patch)
tree6427257fe101016ef07ba28903d65d8f8be8e2ca /include/linux/fs_pin.h
parent1629d0eb3ead0e0c49e4402049ec7b5b31b81cd7 (diff)
downloadlinux-efb170c22867cdc6f770de441bdefecec6712199.tar.xz
take fs_pin stuff to fs/*
Add a new field to fs_pin - kill(pin). That's what umount and r/o remount will be calling for all pins attached to vfsmount and superblock resp. Called after bumping the refcount, so it won't go away under us. Dropping the refcount is responsibility of the instance. All generic stuff moved to fs/fs_pin.c; the next step will rip all the knowledge of kernel/acct.c from fs/super.c and fs/namespace.c. After that - death to mnt_pin(); it was intended to be usable as generic mechanism for code that wants to attach objects to vfsmount, so that they would not make the sucker busy and would get killed on umount. Never got it right; it remained acct.c-specific all along. Now it's very close to being killable. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include/linux/fs_pin.h')
-rw-r--r--include/linux/fs_pin.h17
1 files changed, 17 insertions, 0 deletions
diff --git a/include/linux/fs_pin.h b/include/linux/fs_pin.h
new file mode 100644
index 000000000000..f66525e72ccf
--- /dev/null
+++ b/include/linux/fs_pin.h
@@ -0,0 +1,17 @@
+#include <linux/fs.h>
+
+struct fs_pin {
+ atomic_long_t count;
+ union {
+ struct {
+ struct hlist_node s_list;
+ struct hlist_node m_list;
+ };
+ struct rcu_head rcu;
+ };
+ void (*kill)(struct fs_pin *);
+};
+
+void pin_put(struct fs_pin *);
+void pin_remove(struct fs_pin *);
+void pin_insert(struct fs_pin *, struct vfsmount *);