| commit | 27a377db745ed4d11b3b9b340756857cb8dde07f | [log] [tgz] |
|---|---|---|
| author | Josef Bacik <jbacik@fb.com> | Fri Feb 07 13:57:59 2014 -0500 |
| committer | Chris Mason <clm@fb.com> | Sat Feb 08 17:57:15 2014 -0800 |
| tree | 9f2893a3f3751542daad4a70f37e6ea57ec61373 | |
| parent | 8051aa1a3d5aaa7bd4c062cad94d09c3d567ef2e [diff] |
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>