| commit | dc6c5fb3b514221f2e9d21ee626a9d95d3418dff | |
| author | Chris Mason <clm@fb.com> | |
| Tue, 13 Oct 2015 18:06:48 +0000 (13 14:06 -0400) | ||
| committer | Chris Mason <clm@fb.com> | |
| Wed, 14 Oct 2015 01:54:44 +0000 (13 18:54 -0700) | ||
| tree | 1717fc340050baa6b07d20273bcfc457fd55e1b9 | treesnapshot (tar.gz zip) |
| parent | 8eb934591f8bf584969454a658f629cd06e59f3a | commitdiff |
btrfs: fix use after free iterating extrefs
The code for btrfs inode-resolve has never worked properly for
files with enough hard links to trigger extrefs. It was trying to
get the leaf out of a path after freeing the path:
btrfs_release_path(path);
leaf = path->nodes[0];
item_size = btrfs_item_size_nr(leaf, slot);
The fix here is to use the extent buffer we cloned just a little higher
up to avoid deadlocks caused by using the leaf in the path.
Signed-off-by: Chris Mason <clm@fb.com>
cc: stable@vger.kernel.org # v3.7+
cc: Mark Fasheh <mfasheh@suse.de>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Mark Fasheh <mfasheh@suse.de>
The code for btrfs inode-resolve has never worked properly for
files with enough hard links to trigger extrefs. It was trying to
get the leaf out of a path after freeing the path:
btrfs_release_path(path);
leaf = path->nodes[0];
item_size = btrfs_item_size_nr(leaf, slot);
The fix here is to use the extent buffer we cloned just a little higher
up to avoid deadlocks caused by using the leaf in the path.
Signed-off-by: Chris Mason <clm@fb.com>
cc: stable@vger.kernel.org # v3.7+
cc: Mark Fasheh <mfasheh@suse.de>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Mark Fasheh <mfasheh@suse.de>
| fs/btrfs/backref.c | diffblobblamehistory |