summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent-tree.c
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2013-01-31 10:23:04 -0500
committerJosef Bacik <jbacik@fusionio.com>2013-02-20 12:59:11 -0500
commit0f5d42b287f32417e54485d79f2318cf2970b37d (patch)
tree6f66c857c212a5d8faa4347c0f1d331e47492c01 /fs/btrfs/extent-tree.c
parent0448748849ef7c593be40e2c1404f7974bd3aac6 (diff)
downloadop-kernel-dev-0f5d42b287f32417e54485d79f2318cf2970b37d.zip
op-kernel-dev-0f5d42b287f32417e54485d79f2318cf2970b37d.tar.gz
Btrfs: remove extent mapping if we fail to add chunk
I got a double free error when unmounting a file system that failed to add a chunk during its operation. This is because we will kfree the mapping that we created but leave the extent_map in the em_tree for chunks. So to fix this just remove the extent_map when we error out so we don't run into this problem. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'fs/btrfs/extent-tree.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud