diff options
author | Boaz Harrosh <bharrosh@panasas.com> | 2009-08-19 17:56:46 +0300 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2009-09-24 07:47:38 -0400 |
commit | 1ba50bbe93ebb98e83b174a85eff76af430c4e5b (patch) | |
tree | 4c7b7db057fa5ca60a4e1adcb5dfb63cbf5a5702 /fs/block_dev.c | |
parent | 88a0a53d702b1fa39ed9e631939d2dbd92dfe486 (diff) | |
download | linux-stable-1ba50bbe93ebb98e83b174a85eff76af430c4e5b.tar.gz linux-stable-1ba50bbe93ebb98e83b174a85eff76af430c4e5b.tar.bz2 linux-stable-1ba50bbe93ebb98e83b174a85eff76af430c4e5b.zip |
exofs: remove BKL from super operations
the two places inside exofs that where taking the BKL were:
exofs_put_super() - .put_super
and
exofs_sync_fs() - which is .sync_fs and is also called from
.write_super.
Now exofs_sync_fs() is protected from itself by also taking
the sb_lock.
exofs_put_super() directly calls exofs_sync_fs() so there is no
danger between these two either.
In anyway there is absolutely nothing dangerous been done
inside exofs_sync_fs().
Unless there is some subtle race with the actual lifetime of
the super_block in regard to .put_super and some other parts
of the VFS. Which is highly unlikely.
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/block_dev.c')
0 files changed, 0 insertions, 0 deletions