summaryrefslogtreecommitdiffstats
path: root/fs/isofs/isofs.h
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2011-07-21 22:22:25 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2011-07-22 19:42:12 -0400
commitd769b3c2ab7184ddd42056595b627cc871caa90e (patch)
treeb030270648c2a2aca7c5417e2ae0436ec7d0a31c /fs/isofs/isofs.h
parent22ba747f660c0acd14761628c24aa972d18058a0 (diff)
downloadop-kernel-dev-d769b3c2ab7184ddd42056595b627cc871caa90e.zip
op-kernel-dev-d769b3c2ab7184ddd42056595b627cc871caa90e.tar.gz
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 'fs/isofs/isofs.h')
-rw-r--r--fs/isofs/isofs.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/isofs/isofs.h b/fs/isofs/isofs.h
index 2882dc0..7d33de8 100644
--- a/fs/isofs/isofs.h
+++ b/fs/isofs/isofs.h
@@ -55,7 +55,6 @@ struct isofs_sb_info {
gid_t s_gid;
uid_t s_uid;
struct nls_table *s_nls_iocharset; /* Native language support table */
- struct mutex s_mutex; /* replaces BKL, please remove if possible */
};
#define ISOFS_INVALID_MODE ((mode_t) -1)
OpenPOWER on IntegriCloud