summaryrefslogtreecommitdiff
path: root/fs/btrfs/super.c
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2012-09-14 21:58:59 +0400
committerChris Mason <chris.mason@fusionio.com>2012-10-04 17:40:00 +0400
commit926ced123bd6651b30a07f65a2a8a0b26154cd58 (patch)
tree6ed07ff95d5a0f3f9bae2bc776af9ac88528a135 /fs/btrfs/super.c
parent892951a92ebf8b390815b24f9418f297a5081898 (diff)
downloadlinux-926ced123bd6651b30a07f65a2a8a0b26154cd58.tar.xz
Btrfs: don't do anything in our ->freeze_fs and ->unfreeze_fs
We do not need to do anything special to freeze or unfreeze, it's all taken care of by the generic work, and what we currently have is wrong anyway since we shouldn't be returnning to userspace with mutexes held anyway. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'fs/btrfs/super.c')
-rw-r--r--fs/btrfs/super.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 5aa3b8182d96..fb260bbf59c6 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -1511,17 +1511,11 @@ static long btrfs_control_ioctl(struct file *file, unsigned int cmd,
static int btrfs_freeze(struct super_block *sb)
{
- struct btrfs_fs_info *fs_info = btrfs_sb(sb);
- mutex_lock(&fs_info->transaction_kthread_mutex);
- mutex_lock(&fs_info->cleaner_mutex);
return 0;
}
static int btrfs_unfreeze(struct super_block *sb)
{
- struct btrfs_fs_info *fs_info = btrfs_sb(sb);
- mutex_unlock(&fs_info->cleaner_mutex);
- mutex_unlock(&fs_info->transaction_kthread_mutex);
return 0;
}