linux-dev - Linux kernel development work

Age	Commit message (Collapse)	Author	Files	Lines
2015-01-25	switch the IO-triggering parts of umount to fs_pin	Al Viro	1	-1/+0
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-25	new fs_pin killing logics	Al Viro	1	-6/+48
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-25	allow attaching fs_pin to a group not associated with some superblock	Al Viro	1	-7/+13
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-25	pull bumping refcount into ->kill()	Al Viro	1	-12/+0
	there will be one more change of ->kill() calling conventions; this isn't final. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-01-25	kill pin_put()	Al Viro	1	-11/+0
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-08-07	make fs/{namespace,super}.c forget about acct.h	Al Viro	1	-4/+5
	These externs belong in fs/internal.h. Rename (they are not acct-specific anymore) and move them over there. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-08-07	take fs_pin stuff to fs/*	Al Viro	1	-0/+77
	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>