From: Filipe Manana <fdmanana@suse.com>
Date: Fri, 8 Aug 2014 01:47:06 +0000 (+0100)
Subject: Btrfs: clone, don't create invalid hole extent map
X-Git-Tag: omap-fixes-against-v3.17-rc3~41^2~5
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=62e2390e1ad78f956e96a6a831761adc6f2bf58a;p=pandora-kernel.git

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>
---

Reading git-diff-tree failed