remarkable-linux/fs/hfs
Christoph Hellwig ebc1ac1645 ->write_super lock_super pushdown
Push down lock_super into ->write_super instances and remove it from the
caller.

Following filesystem don't need ->s_lock in ->write_super and are skipped:

 * bfs, nilfs2 - no other uses of s_lock and have internal locks in
	->write_super
 * ext2 - uses BKL in ext2_write_super and has internal calls without s_lock
 * reiserfs - no other uses of s_lock as has reiserfs_write_lock (BKL) in
 	->write_super
 * xfs - no other uses of s_lock and uses internal lock (buffer lock on
	superblock buffer) to serialize ->write_super.  Also xfs_fs_write_super
	is superflous and will go away in the next merge window

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2009-06-11 21:36:09 -04:00
..
attr.c
bfind.c
bitmap.c
bnode.c
brec.c
btree.c
btree.h
catalog.c
dir.c
extent.c
hfs.h
hfs_fs.h constify dentry_operations: misc filesystems 2009-03-27 14:44:00 -04:00
inode.c hfs: fix memory leak when unmounting 2009-04-13 15:04:29 -07:00
Kconfig
Makefile
mdb.c hfs: fix memory leak when unmounting 2009-04-13 15:04:29 -07:00
part_tbl.c
string.c
super.c ->write_super lock_super pushdown 2009-06-11 21:36:09 -04:00
sysdep.c constify dentry_operations: misc filesystems 2009-03-27 14:44:00 -04:00
trans.c