diff options
| author | Jan Kara <jack@suse.cz> | 2011-07-21 22:22:25 +0200 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2011-07-23 01:42:12 +0200 |
| commit | d769b3c2ab7184ddd42056595b627cc871caa90e (patch) | |
| tree | b030270648c2a2aca7c5417e2ae0436ec7d0a31c /fs/open.c | |
| parent | jffs2: fix IN_DELETE_SELF on overwriting rename() killing a directory (diff) | |
| download | linux-d769b3c2ab7184ddd42056595b627cc871caa90e.tar.xz linux-d769b3c2ab7184ddd42056595b627cc871caa90e.zip | |
isofs: Remove global fs lock
sbi->s_mutex isn't needed for isofs at all so we can just remove it. Generally,
since isofs is always mounted read-only, filesystem structure cannot change
under us. So buffer_head contents stays constant after it's filled in. That
leaves us with possible changes of global data structures. Superblock changes
only during filesystem mount (even remount does not change it), inodes are only
filled in during reading from disk. So there are no changes of these structures
to bother about.
Arguments why sbi->s_mutex can be removed at each place:
isofs_readdir: Accesses sb, inode, filp, local variables => s_mutex not needed
isofs_lookup: Protected by directory's i_mutex. Accesses sb, inode, dentry,
local variables => s_mutex not needed
rock_ridge_symlink_readpage: Protected by page lock. Accesses sb, inode,
local variables => s_mutex not needed.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions