summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/disk-io.c
diff options
context:
space:
mode:
authorJeff Mahoney2018-03-20 20:25:25 +0100
committerDavid Sterba2018-03-31 01:41:12 +0200
commitdc2d3005d27da41247d6c42077e335a777afc79c (patch)
tree87f3f93eeae85aa11b53f6e8d26652c27d4632e2 /fs/btrfs/disk-io.c
parentBtrfs: replace: cache rbio when rebuild data on missing device (diff)
downloadkernel-qcow2-linux-dc2d3005d27da41247d6c42077e335a777afc79c.tar.gz
kernel-qcow2-linux-dc2d3005d27da41247d6c42077e335a777afc79c.tar.xz
kernel-qcow2-linux-dc2d3005d27da41247d6c42077e335a777afc79c.zip
btrfs: remove dead create_space_info calls
Since commit 2be12ef79 (btrfs: Separate space_info create/update), we've separated out the creation and updating of the space info structures. That commit was a straightforward refactoring of the two parts of update_space_info, but we can go a step further. Since commits c59021f84 (Btrfs: fix OOPS of empty filesystem after balance) and b742bb82f (Btrfs: Link block groups of different raid types), we know that the space_info structures will be created at mount and there will only ever be, at most, three of them. This patch cleans out the create_space_info calls after __find_space_info returns NULL since __find_space_info *can't* return NULL. The initial cause for reviewing this was the kobject_add calls from create_space_info occuring in sites where fs-reclaim wasn't allowed. Now we are certain they occur only early in the mount process and are safe. Signed-off-by: Jeff Mahoney <jeffm@suse.com> Reviewed-by: Nikolay Borisov <nborisov@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/disk-io.c')
0 files changed, 0 insertions, 0 deletions