hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
linux-sg2042/include/linux/fs_pin.h

25 lines
580 B
C
Raw Normal View History

new fs_pin killing logics Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 06:53:21 +08:00
#include <linux/wait.h>
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>
2014-08-07 20:39:04 +08:00
struct fs_pin {
new fs_pin killing logics Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 06:53:21 +08:00
wait_queue_head_t wait;
int done;
take count and rcu_head out of fs_pin Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 01:47:38 +08:00
struct hlist_node s_list;
struct hlist_node m_list;
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>
2014-08-07 20:39:04 +08:00
void (*kill)(struct fs_pin *);
};
new fs_pin killing logics Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 06:53:21 +08:00
struct vfsmount;
static inline void init_fs_pin(struct fs_pin *p, void (*kill)(struct fs_pin *))
{
init_waitqueue_head(&p->wait);
fs_pin: Allow for the possibility that m_list or s_list go unused. 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-04-03 05:35:48 +08:00
INIT_HLIST_NODE(&p->s_list);
INIT_HLIST_NODE(&p->m_list);
new fs_pin killing logics Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 06:53:21 +08:00
p->kill = kill;
}
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>
2014-08-07 20:39:04 +08:00
void pin_remove(struct fs_pin *);
allow attaching fs_pin to a group not associated with some superblock Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 23:57:27 +08:00
void pin_insert_group(struct fs_pin *, struct vfsmount *, struct hlist_head *);
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>
2014-08-07 20:39:04 +08:00
void pin_insert(struct fs_pin *, struct vfsmount *);
new fs_pin killing logics Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-11 06:53:21 +08:00
void pin_kill(struct fs_pin *);