summaryrefslogtreecommitdiff
path: root/include/linux/fs_pin.h
AgeCommit message (Collapse)AuthorFilesLines
2015-04-09fs_pin: Allow for the possibility that m_list or s_list go unused.Eric W. Biederman1-0/+2
This is needed to support lazily umounting locked mounts. Because the entire unmounted subtree needs to stay together until there are no users with references to any part of the subtree. To support this guarantee that the fs_pin m_list and s_list nodes are initialized by initializing them in init_fs_pin allowing for the possibility that pin_insert_group does not touch them. Further use hlist_del_init in pin_remove so that there is a hlist_unhashed test before the list we attempt to update the previous list item. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
2015-01-26new fs_pin killing logicsAl Viro1-1/+12
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-26allow attaching fs_pin to a group not associated with some superblockAl Viro1-0/+1
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-26take count and rcu_head out of fs_pinAl Viro1-8/+2
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-26kill pin_put()Al Viro1-1/+0
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-08-07take fs_pin stuff to fs/*Al Viro1-0/+17
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>