Btrfs: clone, don't create invalid hole extent map
authorFilipe Manana <fdmanana@suse.com>
Fri, 8 Aug 2014 01:47:06 +0000 (02:47 +0100)
committerChris Mason <clm@fb.com>
Thu, 21 Aug 2014 14:55:26 +0000 (07:55 -0700)
commit62e2390e1ad78f956e96a6a831761adc6f2bf58a
tree293bff9b4dcc58b928271a36a0421455aaf07ee1
parent7064dd5c36187725e7ccfd837e07678ae435d3f5
Btrfs: clone, don't create invalid hole extent map

When cloning a file that consists of an inline extent, we were creating
an extent map that represents a non-existing trailing hole starting at a
file offset that isn't a multiple of the sector size. This happened because
when processing an inline extent we weren't aligning the extent's length to
the sector size, and therefore incorrectly treating the range
[inline_extent_length; sector_size[ as a hole.

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Signed-off-by: Chris Mason <clm@fb.com>
fs/btrfs/ioctl.c