xfs: don't set XFS_BTCUR_BPRV_WASDEL in xfs_bunmapi
The XFS_BTCUR_BPRV_WASDEL flag is supposed to indicate that we are converting a delayed allocation to a real one, which isn't the case in xfs_bunmapi. Setting it could theoretically lead to misaccounting here, but it's unlikely that we ever hit it in practice. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
This commit is contained in:
parent
e3f0f7563e
commit
b213d69293
|
@ -5723,11 +5723,7 @@ __xfs_bunmapi(
|
|||
XFS_QMOPT_RES_REGBLKS);
|
||||
}
|
||||
ip->i_delayed_blks -= del.br_blockcount;
|
||||
if (cur)
|
||||
cur->bc_private.b.flags |=
|
||||
XFS_BTCUR_BPRV_WASDEL;
|
||||
} else if (cur)
|
||||
cur->bc_private.b.flags &= ~XFS_BTCUR_BPRV_WASDEL;
|
||||
}
|
||||
|
||||
error = xfs_bmap_del_extent(ip, tp, &lastx, dfops, cur, &del,
|
||||
&tmp_logflags, whichfork, flags);
|
||||
|
|
Loading…
Reference in a new issue