From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Hellwig <hch@lst.de>,
clm@fb.com, josef@toxicpanda.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: move all btree initialization into btrfs_init_btree_inode
Date: Wed, 14 Feb 2024 16:58:55 +1030 [thread overview]
Message-ID: <7fbe36d5-3ebb-4daa-9c92-0761ba49686b@gmx.com> (raw)
In-Reply-To: <20230219181022.3499088-1-hch@lst.de>
在 2023/2/20 04:40, Christoph Hellwig 写道:
> Move the remaining code that deals with initializing the btree
> inode into btrfs_init_btree_inode instead of splitting it between
> that helpers and its only caller.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Just one small nitpick.
> ---
> fs/btrfs/disk-io.c | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index b53f0e30ce2b3b..981973b40b065a 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2125,11 +2125,16 @@ static void btrfs_init_balance(struct btrfs_fs_info *fs_info)
> atomic_set(&fs_info->reloc_cancel_req, 0);
> }
>
> -static void btrfs_init_btree_inode(struct btrfs_fs_info *fs_info)
> +static int btrfs_init_btree_inode(struct super_block *sb)
It's preferred to use btrfs_fs_info * as a parameter, just to keep the
consistency of all btrfs interfaces.
Thanks,
Qu
> {
> - struct inode *inode = fs_info->btree_inode;
> + struct btrfs_fs_info *fs_info = btrfs_sb(sb);
> unsigned long hash = btrfs_inode_hash(BTRFS_BTREE_INODE_OBJECTID,
> fs_info->tree_root);
> + struct inode *inode;
> +
> + inode = new_inode(sb);
> + if (!inode)
> + return -ENOMEM;
>
> inode->i_ino = BTRFS_BTREE_INODE_OBJECTID;
> set_nlink(inode, 1);
> @@ -2140,6 +2145,7 @@ static void btrfs_init_btree_inode(struct btrfs_fs_info *fs_info)
> */
> inode->i_size = OFFSET_MAX;
> inode->i_mapping->a_ops = &btree_aops;
> + mapping_set_gfp_mask(inode->i_mapping, GFP_NOFS);
>
> RB_CLEAR_NODE(&BTRFS_I(inode)->rb_node);
> extent_io_tree_init(fs_info, &BTRFS_I(inode)->io_tree,
> @@ -2152,6 +2158,8 @@ static void btrfs_init_btree_inode(struct btrfs_fs_info *fs_info)
> BTRFS_I(inode)->location.offset = 0;
> set_bit(BTRFS_INODE_DUMMY, &BTRFS_I(inode)->runtime_flags);
> __insert_inode_hash(inode, hash);
> + fs_info->btree_inode = inode;
> + return 0;
> }
>
> static void btrfs_init_dev_replace_locks(struct btrfs_fs_info *fs_info)
> @@ -3351,13 +3359,9 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
> goto fail;
> }
>
> - fs_info->btree_inode = new_inode(sb);
> - if (!fs_info->btree_inode) {
> - err = -ENOMEM;
> + err = btrfs_init_btree_inode(sb);
> + if (err)
> goto fail;
> - }
> - mapping_set_gfp_mask(fs_info->btree_inode->i_mapping, GFP_NOFS);
> - btrfs_init_btree_inode(fs_info);
>
> invalidate_bdev(fs_devices->latest_dev->bdev);
>
next prev parent reply other threads:[~2024-02-14 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 18:10 [PATCH] btrfs: move all btree initialization into btrfs_init_btree_inode Christoph Hellwig
2023-02-20 8:17 ` Johannes Thumshirn
2023-02-20 20:19 ` David Sterba
2023-02-21 14:28 ` Christoph Hellwig
2023-02-21 14:51 ` David Sterba
2023-02-27 7:35 ` Anand Jain
2023-02-27 13:39 ` Christoph Hellwig
2023-02-27 18:41 ` David Sterba
2024-02-14 6:28 ` Qu Wenruo [this message]
2024-02-14 7:12 ` David Sterba
2024-02-14 8:32 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fbe36d5-3ebb-4daa-9c92-0761ba49686b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox