diff options
| author | Josef Bacik <jbacik@fusionio.com> | 2012-11-07 13:44:13 -0500 |
|---|---|---|
| committer | Chris Mason <chris.mason@fusionio.com> | 2012-12-16 20:46:27 -0500 |
| commit | 5124e00ec5b0be56155a11aec416fcc5125339f1 (patch) | |
| tree | edf9d51c481b4b7cf62a47986d13227ec36c541e /fs/btrfs | |
| parent | 0b1c6ccadee4ea4adb98799f3430fc72e57a187f (diff) | |
| download | op-kernel-dev-5124e00ec5b0be56155a11aec416fcc5125339f1.zip op-kernel-dev-5124e00ec5b0be56155a11aec416fcc5125339f1.tar.gz | |
Btrfs: only unlock and relock if we have to
I noticed while doing fsync tests that we were always dropping the path and
re-searching when we first cow the log root even though we've already gotten
the write lock on the root. That's because we don't take into account that
there might not be a parent node, so fix the check to make sure there is
actually a parent node before we undo all of this work for nothing. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'fs/btrfs')
| -rw-r--r-- | fs/btrfs/ctree.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c index e7bea1d..c7b67cf 100644 --- a/fs/btrfs/ctree.c +++ b/fs/btrfs/ctree.c @@ -2564,7 +2564,10 @@ again: * must have write locks on this node and the * parent */ - if (level + 1 > write_lock_level) { + if (level > write_lock_level || + (level + 1 > write_lock_level && + level + 1 < BTRFS_MAX_LEVEL && + p->nodes[level + 1])) { write_lock_level = level + 1; btrfs_release_path(p); goto again; |
