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 <bo.liu@linux.alibaba.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
index 1f71695cb0a80288e4a3256bcd9167dc03efb15a..1124d236291d75b12a2f2fae5a3060f6efbc0e67 100644 (file)
--- a/fs/btrfs/ctree.c
+++ b/fs/btrfs/ctree.c
@@ -2910,7 +2910,7 @@ cow_done:
                        }
                        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;
                }
        }