openslx/kernel-qcow2-linux.git - In-kernel qcow2 (Kernel part)

	Commit message (Collapse)	Author	Age	Files	Lines
*	new fs_pin killing logics	Al Viro	2015-01-26	1	-1/+12
\| \| \| \|	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
*	allow attaching fs_pin to a group not associated with some superblock	Al Viro	2015-01-26	1	-0/+1
\| \| \| \|	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
*	take count and rcu_head out of fs_pin	Al Viro	2015-01-26	1	-8/+2
\| \| \| \|	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
*	kill pin_put()	Al Viro	2015-01-26	1	-1/+0
\| \| \| \|	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
*	take fs_pin stuff to fs/*	Al Viro	2014-08-07	1	-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>