btrfs: Remove stale comment about select_delayed_ref
authorNikolay Borisov <nborisov@suse.com>
Thu, 17 May 2018 11:16:29 +0000 (14:16 +0300)
committerDavid Sterba <dsterba@suse.com>
Mon, 28 May 2018 16:23:42 +0000 (18:23 +0200)
select_delayed_ref really just gets the next delayed ref which has to
be processed - either an add ref or drop ref. We never go back for
anything. So the comment is actually bogus, just remove it.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent-tree.c

index fa2ed14532c1fc1e06625442e4493fc03e79e30a..47edb3af3f9f422a2c928800278d888cea9fab88 100644 (file)
@@ -2705,10 +2705,6 @@ static noinline int __btrfs_run_delayed_refs(struct btrfs_trans_handle *trans,
                spin_lock(&locked_ref->lock);
                btrfs_merge_delayed_refs(trans, delayed_refs, locked_ref);
 
-               /*
-                * locked_ref is the head node, so we have to go one
-                * node back for any delayed ref updates
-                */
                ref = select_delayed_ref(locked_ref);
 
                if (ref && ref->seq &&