summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fb.com>2014-02-07 13:57:59 -0500
committerChris Mason <clm@fb.com>2014-02-08 17:57:15 -0800
commit27a377db745ed4d11b3b9b340756857cb8dde07f (patch)
tree9f2893a3f3751542daad4a70f37e6ea57ec61373 /fs
parent8051aa1a3d5aaa7bd4c062cad94d09c3d567ef2e (diff)
downloadop-kernel-dev-27a377db745ed4d11b3b9b340756857cb8dde07f.zip
op-kernel-dev-27a377db745ed4d11b3b9b340756857cb8dde07f.tar.gz
Btrfs: don't loop forever if we can't run because of the tree mod log
A user reported a 100% cpu hang with my new delayed ref code. Turns out I forgot to increase the count check when we can't run a delayed ref because of the tree mod log. If we can't run any delayed refs during this there is no point in continuing to look, and we need to break out. Thanks, Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs')
-rw-r--r--fs/btrfs/extent-tree.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 9c9ecc9..32312e0 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -2385,6 +2385,7 @@ static noinline int __btrfs_run_delayed_refs(struct btrfs_trans_handle *trans,
spin_unlock(&delayed_refs->lock);
locked_ref = NULL;
cond_resched();
+ count++;
continue;
}
OpenPOWER on IntegriCloud