xfs: inode fork allocation depends on XFS_IFEXTENT flag
Due to confusion on when the XFS_IFEXTENT needs to be set, the changes ine6a688c332
("xfs: initialise attr fork on inode create") failed to set the flag when initialising the empty attribute fork at inode creation. Set this flag the same way xfs_bmap_add_attrfork() does after attry fork allocation. Fixes:e6a688c332
("xfs: initialise attr fork on inode create") Signed-off-by: Dave Chinner <dchinner@redhat.com> Tested-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
This commit is contained in:
parent
2442ee15bb
commit
8de1cb0038
|
@ -875,6 +875,7 @@ xfs_init_new_inode(
|
|||
if (init_xattrs && xfs_sb_version_hasattr(&mp->m_sb)) {
|
||||
ip->i_forkoff = xfs_default_attroffset(ip) >> 3;
|
||||
ip->i_afp = xfs_ifork_alloc(XFS_DINODE_FMT_EXTENTS, 0);
|
||||
ip->i_afp->if_flags = XFS_IFEXTENTS;
|
||||
}
|
||||
|
||||
/*
|
||||
|
|
Loading…
Reference in New Issue