diff options
author | 2025-04-28 10:06:50 +0930 | |
---|---|---|
committer | 2025-05-15 14:30:50 +0200 | |
commit | 63f32b7b5d5a9107d04fb11cc85d5cd695f85e19 (patch) | |
tree | 9121aafa1d9ddde94f1e51d69c115273cd505456 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | btrfs: get rid of goto in alloc_test_extent_buffer() (diff) | |
download | linux-rng-63f32b7b5d5a9107d04fb11cc85d5cd695f85e19.tar.xz linux-rng-63f32b7b5d5a9107d04fb11cc85d5cd695f85e19.zip |
btrfs: merge btrfs_read_dev_one_super() into btrfs_read_disk_super()
We have two functions to read a super block from a block device:
- btrfs_read_dev_one_super()
Exported from disk-io.c
- btrfs_read_disk_super()
Local to volumes.c
And they have some minor differences:
- btrfs_read_dev_one_super() uses @copy_num
Meanwhile btrfs_read_disk_super() relies on the physical and expected
bytenr passed from the caller.
The parameter list of btrfs_read_dev_one_super() is more user
friendly.
- btrfs_read_disk_super() makes sure the label is NUL terminated
We do not need two different functions doing the same job, so merge the
behavior into btrfs_read_disk_super() by:
- Remove btrfs_read_dev_one_super()
- Export btrfs_read_disk_super()
The name pairs with btrfs_release_disk_super() perfectly.
- Change the parameter list of btrfs_read_disk_super() to mimic
btrfs_read_dev_one_super()
All existing callers are calculating the physical address and expect
bytenr before calling btrfs_read_disk_super() already.
Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions