diff options
author | Christoph Hellwig <hch@lst.de> | 2025-06-11 12:03:00 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2025-07-22 00:06:19 +0200 |
commit | 9f43d0ff55e306aed9fa95c79ed372d530471382 (patch) | |
tree | 0762e77df141be5dac9edc1032bac708cacc81a7 /tools/perf/scripts/python/stackcollapse.py | |
parent | 2936a6ac8d976f3c4de6fb5fbc00c5905c0cfec7 (diff) |
btrfs: call btrfs_close_devices() from ->kill_sb
Although btrfs is not yet implementing blk_holder_ops, there is a
requirement for proper blk_holder_ops:
- blkdev_put() must not be called under sb->s_umount
The blkdev_put()/bdev_fput() must not be called under sb->s_umount to
avoid lock order reversal with disk->open_mutex.
This is for the proper blk_holder_ops callbacks.
Currently we're fine because we call regular fput() which defers the
blk holder reclaiming.
To prepare for the future of blk_holder_ops, move the
btrfs_close_devices() calls into btrfs_free_fs_info().
That will be called from kill_sb() callbacks, which is also called for
error handing during mount failures, or there is already an existing
super block.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions