tree c428134cc3f86ec4e3dd48c413eee15995d5bfc0
parent 4a3560c4f3f0f92d3b673944753e3e947e030bc4
author Mark Fasheh <mfasheh@suse.de> 1435700526 -0700
committer Chris Mason <clm@fb.com> 1439130865 -0700

btrfs: fix clone / extent-same deadlocks

Clone and extent same lock their source and target inodes in opposite order.
In addition to this, the range locking in clone doesn't take ordering into
account. Fix this by having clone use the same locking helpers as
btrfs-extent-same.

In addition, I do a small cleanup of the locking helpers, removing a case
(both inodes being the same) which was poorly accounted for and never
actually used by the callers.

Signed-off-by: Mark Fasheh <mfasheh@suse.de>
Reviewed-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Chris Mason <clm@fb.com>