diff options
author | 2020-01-24 09:32:59 -0500 | |
---|---|---|
committer | 2020-03-23 17:01:33 +0100 | |
commit | 8260edba67a2e6bd5e709d32188e23aa22cb4a38 (patch) | |
tree | 38001d94d551e57172cfb1933c56087a51bb0118 /fs/btrfs/tree-log.c | |
parent | btrfs: move fs_info init work into it's own helper function (diff) | |
download | wireguard-linux-8260edba67a2e6bd5e709d32188e23aa22cb4a38.tar.xz wireguard-linux-8260edba67a2e6bd5e709d32188e23aa22cb4a38.zip |
btrfs: make the init of static elements in fs_info separate
In adding things like eb leak checking and root leak checking there were
a lot of weird corner cases that come from the fact that
1) We do not init the fs_info until we get to open_ctree time in the
normal case and
2) The test infrastructure half-init's the fs_info for things that it
needs.
This makes it really annoying to make changes because you have to add
init in two different places, have special cases for testing fs_info's
that may not have certain things initialized, and cases for fs_info's
that didn't make it to open_ctree and thus are not fully set up.
Fix this by extracting out the non-allocating init of the fs info into
it's own public function and use that to make sure we're all getting
consistent views of an allocated fs_info.
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/tree-log.c')
0 files changed, 0 insertions, 0 deletions