diff options
| author | Yang Xu <xuyang2018.jy@fujitsu.com> | 2021-12-21 18:38:19 +0100 |
|---|---|---|
| committer | Darrick J. Wong <djwong@kernel.org> | 2021-12-21 18:49:41 +0100 |
| commit | 132c460e49649685bf4b02ba43dea59062f797d9 (patch) | |
| tree | c70e73e2338f8228aed8db657499132529dc5cd3 /fs/xfs | |
| parent | xfs: check sb_meta_uuid for dabuf buffer recovery (diff) | |
| download | linux-132c460e49649685bf4b02ba43dea59062f797d9.tar.xz linux-132c460e49649685bf4b02ba43dea59062f797d9.zip | |
xfs: Fix comments mentioning xfs_ialloc
Since kernel commit 1abcf261016e ("xfs: move on-disk inode allocation out of xfs_ialloc()"),
xfs_ialloc has been renamed to xfs_init_new_inode. So update this in comments.
Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Diffstat (limited to 'fs/xfs')
| -rw-r--r-- | fs/xfs/xfs_icache.c | 3 | ||||
| -rw-r--r-- | fs/xfs/xfs_iops.c | 6 |
2 files changed, 5 insertions, 4 deletions
diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c index da4af2142a2b..d019c98eb839 100644 --- a/fs/xfs/xfs_icache.c +++ b/fs/xfs/xfs_icache.c @@ -749,7 +749,8 @@ again: /* * If we have a real type for an on-disk inode, we can setup the inode - * now. If it's a new inode being created, xfs_ialloc will handle it. + * now. If it's a new inode being created, xfs_init_new_inode will + * handle it. */ if (xfs_iflags_test(ip, XFS_INEW) && VFS_I(ip)->i_mode != 0) xfs_setup_existing_inode(ip); diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c index 72bdd7c79e93..3447c19e99da 100644 --- a/fs/xfs/xfs_iops.c +++ b/fs/xfs/xfs_iops.c @@ -1303,9 +1303,9 @@ xfs_diflags_to_iflags( * Initialize the Linux inode. * * When reading existing inodes from disk this is called directly from xfs_iget, - * when creating a new inode it is called from xfs_ialloc after setting up the - * inode. These callers have different criteria for clearing XFS_INEW, so leave - * it up to the caller to deal with unlocking the inode appropriately. + * when creating a new inode it is called from xfs_init_new_inode after setting + * up the inode. These callers have different criteria for clearing XFS_INEW, so + * leave it up to the caller to deal with unlocking the inode appropriately. */ void xfs_setup_inode( |