summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/inode.c
diff options
context:
space:
mode:
authorBoris Burkov <boris@bur.io>2023-07-20 12:05:28 -0700
committerDavid Sterba <dsterba@suse.com>2023-10-12 16:44:12 +0200
commite076145115c0b5df838ced18294a3d7d92d66ef7 (patch)
treec4f14a06d133be907158ef0a4fb9e705bea87b4d /fs/btrfs/inode.c
parent2672a051e3847401b80ed4e89c7af5be6b3f1be0 (diff)
downloadlinux-stable-e076145115c0b5df838ced18294a3d7d92d66ef7.tar.gz
linux-stable-e076145115c0b5df838ced18294a3d7d92d66ef7.tar.bz2
linux-stable-e076145115c0b5df838ced18294a3d7d92d66ef7.zip
btrfs: qgroup: only set QUOTA_ENABLED when done reading qgroups
In open_ctree, we set BTRFS_FS_QUOTA_ENABLED as soon as we see a quota_root, as opposed to after we are done setting up the qgroup structures. In the quota_enable path, we wait until after the structures are set up. Likewise, in disable, we clear the bit before tearing down the structures. I feel that this organization is less surprising for the open_ctree path. I don't believe this fixes any actual bug, but avoids potential confusion when using btrfs_qgroup_mode in an intermediate state where we are enabled but haven't yet setup the qgroup status flags. It also avoids any risk of calling a qgroup function and attempting to use the qgroup rbtrees before they exist/are setup. This all occurs before we do rw setup, so I believe it should be mostly a no-op. Signed-off-by: Boris Burkov <boris@bur.io> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/inode.c')
0 files changed, 0 insertions, 0 deletions