xfs: Check for extent overflow when punching a hole
The extent mapping the file offset at which a hole has to be inserted will be split into two extents causing extent count to increase by 1. Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Allison Henderson <allison.henderson@oracle.com> Signed-off-by: Chandan Babu R <chandanrlinux@gmail.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
This commit is contained in:
committed by
Darrick J. Wong
parent
727e1acd29
commit
85ef08b5a6
@@ -891,6 +891,11 @@ xfs_unmap_extent(
|
||||
|
||||
xfs_trans_ijoin(tp, ip, 0);
|
||||
|
||||
error = xfs_iext_count_may_overflow(ip, XFS_DATA_FORK,
|
||||
XFS_IEXT_PUNCH_HOLE_CNT);
|
||||
if (error)
|
||||
goto out_trans_cancel;
|
||||
|
||||
error = xfs_bunmapi(tp, ip, startoffset_fsb, len_fsb, 0, 2, done);
|
||||
if (error)
|
||||
goto out_trans_cancel;
|
||||
@@ -1168,6 +1173,11 @@ xfs_insert_file_space(
|
||||
xfs_ilock(ip, XFS_ILOCK_EXCL);
|
||||
xfs_trans_ijoin(tp, ip, 0);
|
||||
|
||||
error = xfs_iext_count_may_overflow(ip, XFS_DATA_FORK,
|
||||
XFS_IEXT_PUNCH_HOLE_CNT);
|
||||
if (error)
|
||||
goto out_trans_cancel;
|
||||
|
||||
/*
|
||||
* The extent shifting code works on extent granularity. So, if stop_fsb
|
||||
* is not the starting block of extent, we need to split the extent at
|
||||
|
||||
Reference in New Issue
Block a user