diff options
author | Josef Bacik <josef@toxicpanda.com> | 2020-02-14 16:11:42 -0500 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2020-03-23 17:01:59 +0100 |
commit | 8c38938c7bb096313ad00c2bafa82af37636b0ec (patch) | |
tree | 6b364d2d7720b841cf368693aa077ecb2dcba386 /fs/btrfs/export.h | |
parent | 0e996e7fcf2e3a7a5d13b0ed5f9cebc551bd94ba (diff) | |
download | linux-rpi-8c38938c7bb096313ad00c2bafa82af37636b0ec.tar.gz linux-rpi-8c38938c7bb096313ad00c2bafa82af37636b0ec.tar.bz2 linux-rpi-8c38938c7bb096313ad00c2bafa82af37636b0ec.zip |
btrfs: move the root freeing stuff into btrfs_put_root
There are a few different ways to free roots, either you allocated them
yourself and you just do
free_extent_buffer(root->node);
free_extent_buffer(root->commit_node);
btrfs_put_root(root);
Which is the pattern for log roots. Or for snapshots/subvolumes that
are being dropped you simply call btrfs_free_fs_root() which does all
the cleanup for you.
Unify this all into btrfs_put_root(), so that we don't free up things
associated with the root until the last reference is dropped. This
makes the root freeing code much more significant.
The only caveat is at close_ctree() time we have to free the extent
buffers for all of our main roots (extent_root, chunk_root, etc) because
we have to drop the btree_inode and we'll run into issues if we hold
onto those nodes until ->kill_sb() time. This will be addressed in the
future when we kill the btree_inode.
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/export.h')
0 files changed, 0 insertions, 0 deletions