diff options
author | 2017-05-22 09:35:49 +0300 | |
---|---|---|
committer | 2017-06-19 18:26:00 +0200 | |
commit | 2be12ef79fe9f5333cb9fadc85ef20b6832a56d7 (patch) | |
tree | ce415bb63e2db297a99d78d2242bce5404e985aa /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | Btrfs: let btrfs_print_leaf print more about block group (diff) | |
download | linux-dev-2be12ef79fe9f5333cb9fadc85ef20b6832a56d7.tar.xz linux-dev-2be12ef79fe9f5333cb9fadc85ef20b6832a56d7.zip |
btrfs: Separate space_info create/update
Currently the struct space_info creation code is intermixed in the
udpate_space_info function. There are well-defined points at which the
we actually want to create brand-new space_info structs (e.g. during
mount of the filesystem as well as sometimes when adding/initialising
new chunks). In such cases update_space_info is called with 0 as the
bytes parameter. All of this makes for spaghetti code.
Fix it by factoring out the creation code in a separate
create_space_info structure. This also allows to simplify the internals.
Also remove BUG_ON from do_alloc_chunk since the callers handle errors.
Furthermore it will make the update_space_info function not fail,
allowing us to remove error handling in callers. This will come in a
follow up patch.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Jeff Mahoney <jeffm@suse.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions