On Mon, Jun 22, 2015 at 03:47:40PM -0700, Mark Fasheh wrote: > 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@xxxxxxx> Reviewed-by: David Sterba <dsterba@xxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
