summaryrefslogtreecommitdiff
path: root/fs/btrfs/extent-io-tree.h
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2023-09-22 11:39:03 +0100
committerDavid Sterba <dsterba@suse.com>2023-10-12 16:44:14 +0200
commitbea22a58c9f39ef426ff76b570d93111882152ec (patch)
treee537c036e7aec4f23c2dee4636570d1a535618e9 /fs/btrfs/extent-io-tree.h
parentc91ea4bfa6dda549295ea7c15dfc990094d1fcd3 (diff)
downloadlwn-bea22a58c9f39ef426ff76b570d93111882152ec.tar.gz
lwn-bea22a58c9f39ef426ff76b570d93111882152ec.zip
btrfs: update stale comment at extent_io_tree_release()
There's this comment at extent_io_tree_release() that mentions io btrees, but this function is no longer used only for io btrees. Originally it was added as a static function named clear_btree_io_tree() at transaction.c, in commit 663dfbb07774 ("Btrfs: deal with convert_extent_bit errors to avoid fs corruption"), as it was used only for cleaning one of the io trees that track dirty extent buffers, the dirty_log_pages io tree of a a root and the dirty_pages io tree of a transaction. Later it was renamed and exported and now it's used to cleanup other io trees such as the allocation state io tree of a device or the csums range io tree of a log root. So remove that comment and replace it with one at the top of the function that is more complete, mentioning what the function does and that it's expected to be called only when a task is sure no one else will need to use the tree anymore, as well as there should be no locked ranges in the tree and therefore no waiters on its extent state records. Also add an assertion to check that there are no locked extent state records in the tree. Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent-io-tree.h')
0 files changed, 0 insertions, 0 deletions