Filipe David Borba Manana
2013-Nov-19 16:19 UTC
[PATCH] Btrfs: fix ordered extent check in btrfs_punch_hole
If the ordered extent''s last byte was 1 less than our region''s start byte, we would unnecessarily wait for the completion of that ordered extent, because it doesn''t intersect our target range. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> --- fs/btrfs/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index c77da44..a679a36 100644 --- a/fs/btrfs/file.c +++ b/fs/btrfs/file.c @@ -2129,7 +2129,7 @@ static int btrfs_punch_hole(struct inode *inode, loff_t offset, loff_t len) * we need to try again. */ if ((!ordered || - (ordered->file_offset + ordered->len < lockstart || + (ordered->file_offset + ordered->len <= lockstart || ordered->file_offset > lockend)) && !test_range_bit(&BTRFS_I(inode)->io_tree, lockstart, lockend, EXTENT_UPTODATE, 0, -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html