Btrfs: do not unnecessarily pass write_lock_level when processing leaf

As we're going to return right after the call, it's not necessary to get update the new write_lock_level from unlock_up. Signed-off-by: Liu Bo <[email protected]> Reviewed-by: David Sterba <[email protected]> Signed-off-by: David Sterba <[email protected]>
mrcsosa · Oct 15, 2018 · 4b6f8e9 · 4b6f8e9
1 parent 4fd786e
commit 4b6f8e9
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
@@ -2910,7 +2910,7 @@ int btrfs_search_slot(struct btrfs_trans_handle *trans, struct btrfs_root *root,
 			}
 			if (!p->search_for_split)
 				unlock_up(p, level, lowest_unlock,
-					  min_write_lock_level, &write_lock_level);
+					  min_write_lock_level, NULL);
 			goto done;
 		}
 	}