Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9a0ec83d authored by Nikolay Borisov's avatar Nikolay Borisov Committed by David Sterba
Browse files

btrfs: use WARN_ON in a canonical form btrfs_remove_block_group 



There is no point in using a construct like 'if (!condition)
WARN_ON(1)'. Use WARN_ON(!condition) directly. No functional changes.

Reviewed-by: default avatarJohannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: default avatarNikolay Borisov <nborisov@suse.com>
Reviewed-by: default avatarDavid Sterba <dsterba@suse.com>
Signed-off-by: default avatarDavid Sterba <dsterba@suse.com>
parent 260e7702

fs/btrfs/extent-tree.c

+3 −6
Original line number Diff line number Diff line
@@ -10869,13 +10869,10 @@ int btrfs_remove_block_group(struct btrfs_trans_handle *trans, 
	}



	spin_lock(&trans->transaction->dirty_bgs_lock);

	if (!list_empty(&block_group->dirty_list)) {

		WARN_ON(1);

	}

	if (!list_empty(&block_group->io_list)) {

		WARN_ON(1);

	}

	WARN_ON(!list_empty(&block_group->dirty_list));

	WARN_ON(!list_empty(&block_group->io_list));

	spin_unlock(&trans->transaction->dirty_bgs_lock);



	btrfs_remove_free_space_cache(block_group);



	spin_lock(&block_group->space_info->lock);