On Tue, Sep 18, 2012 at 05:52:23PM +0800, Liu Bo wrote: > Btrfs uses inclusive range end for lock_extent(), unlock_extent() and > related functions, so we made off-by-one errors in file clone. We're lucky that it's off-by-one in a way that it locks more than it should. The function is full of such calculations, I didn't spot any other instances, but another review round would not harm. 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
