Btrfs: don't loop forever if we can't run because of the tree mod log
authorJosef Bacik <jbacik@fb.com>
Fri, 7 Feb 2014 18:57:59 +0000 (13:57 -0500)
committerChris Mason <clm@fb.com>
Sun, 9 Feb 2014 01:57:15 +0000 (17:57 -0800)
commit27a377db745ed4d11b3b9b340756857cb8dde07f
tree9f2893a3f3751542daad4a70f37e6ea57ec61373
parent8051aa1a3d5aaa7bd4c062cad94d09c3d567ef2e
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>
fs/btrfs/extent-tree.c