summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent_map.c
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2013-03-01 11:47:21 -0500
committerJosef Bacik <jbacik@fusionio.com>2013-03-01 11:47:21 -0500
commit124fe663f93162d17b7e391705cac122101e93d8 (patch)
treee845b288ac0976e24b9a2264c6e21c0142b76237 /fs/btrfs/extent_map.c
parent83c8266acc1d19debbf353a16aabbd892ef99462 (diff)
downloadop-kernel-dev-124fe663f93162d17b7e391705cac122101e93d8.zip
op-kernel-dev-124fe663f93162d17b7e391705cac122101e93d8.tar.gz
Btrfs: delete inline extents when we find them during logging
Apparently when we do inline extents we allow the data to overlap the last chunk of the btrfs_file_extent_item, which means that we can possibly have a btrfs_file_extent_item that isn't actually as large as a btrfs_file_extent_item. This messes with us when we try to overwrite the extent when logging new extents since we expect for it to be the right size. To fix this just delete the item and try to do the insert again which will give us the proper sized btrfs_file_extent_item. This fixes a panic where map_private_extent_buffer would blow up because we're trying to write past the end of the leaf. Thanks, Cc: stable@vger.kernel.org Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'fs/btrfs/extent_map.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud