From: Chandan Babu R <chandanrlinux@gmail.com>
To: linux-xfs@vger.kernel.org
Cc: Chandan Babu R <chandanrlinux@gmail.com>,
darrick.wong@oracle.com, david@fromorbit.com, hch@infradead.org,
allison.henderson@oracle.com, Christoph Hellwig <hch@lst.de>
Subject: [PATCH V10 03/14] xfs: Check for extent overflow when punching a hole
Date: Tue, 3 Nov 2020 20:36:31 +0530 [thread overview]
Message-ID: <20201103150642.2032284-4-chandanrlinux@gmail.com> (raw)
In-Reply-To: <20201103150642.2032284-1-chandanrlinux@gmail.com>
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>
---
fs/xfs/libxfs/xfs_inode_fork.h | 7 +++++++
fs/xfs/xfs_bmap_item.c | 15 +++++++++------
fs/xfs/xfs_bmap_util.c | 10 ++++++++++
3 files changed, 26 insertions(+), 6 deletions(-)
diff --git a/fs/xfs/libxfs/xfs_inode_fork.h b/fs/xfs/libxfs/xfs_inode_fork.h
index 7fc2b129a2e7..bcac769a7df6 100644
--- a/fs/xfs/libxfs/xfs_inode_fork.h
+++ b/fs/xfs/libxfs/xfs_inode_fork.h
@@ -40,6 +40,13 @@ struct xfs_ifork {
*/
#define XFS_IEXT_ADD_NOSPLIT_CNT (1)
+/*
+ * Punching out an extent from the middle of an existing extent can cause the
+ * extent count to increase by 1.
+ * i.e. | Old extent | Hole | Old extent |
+ */
+#define XFS_IEXT_PUNCH_HOLE_CNT (1)
+
/*
* Fork handling.
*/
diff --git a/fs/xfs/xfs_bmap_item.c b/fs/xfs/xfs_bmap_item.c
index 1610d6ad089b..80d828394158 100644
--- a/fs/xfs/xfs_bmap_item.c
+++ b/fs/xfs/xfs_bmap_item.c
@@ -439,6 +439,7 @@ xfs_bui_item_recover(
xfs_exntst_t state;
unsigned int bui_type;
int whichfork;
+ int iext_delta;
int error = 0;
/* Only one mapping operation per BUI... */
@@ -497,12 +498,14 @@ xfs_bui_item_recover(
xfs_ilock(ip, XFS_ILOCK_EXCL);
xfs_trans_ijoin(tp, ip, 0);
- if (bui_type == XFS_BMAP_MAP) {
- error = xfs_iext_count_may_overflow(ip, whichfork,
- XFS_IEXT_ADD_NOSPLIT_CNT);
- if (error)
- goto err_cancel;
- }
+ if (bui_type == XFS_BMAP_MAP)
+ iext_delta = XFS_IEXT_ADD_NOSPLIT_CNT;
+ else
+ iext_delta = XFS_IEXT_PUNCH_HOLE_CNT;
+
+ error = xfs_iext_count_may_overflow(ip, whichfork, iext_delta);
+ if (error)
+ goto err_cancel;
count = bmap->me_len;
error = xfs_trans_log_finish_bmap_update(tp, budp, bui_type, ip,
diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index dcd6e61df711..0776abd0103c 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -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;
@@ -1176,6 +1181,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
--
2.28.0
next prev parent reply other threads:[~2020-11-03 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 15:06 [PATCH V10 00/14] Bail out if transaction can cause extent count to overflow Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 01/14] xfs: Add helper for checking per-inode extent count overflow Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 02/14] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2020-11-03 15:06 ` Chandan Babu R [this message]
2020-11-03 15:06 ` [PATCH V10 04/14] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 05/14] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 06/14] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 07/14] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 08/14] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 09/14] xfs: Check for extent overflow when swapping extents Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 10/14] xfs: Introduce error injection to reduce maximum inode fork extent count Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 11/14] xfs: Remove duplicate assert statement in xfs_bmap_btalloc() Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 12/14] xfs: Compute bmap extent alignments in a separate function Chandan Babu R
2020-11-03 19:51 ` Darrick J. Wong
2020-11-04 3:21 ` Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 13/14] xfs: Process allocated extent " Chandan Babu R
2020-11-03 15:06 ` [PATCH V10 14/14] xfs: Introduce error injection to allocate only minlen size extents for files Chandan Babu R
2020-11-03 19:56 ` Darrick J. Wong
2020-11-04 3:22 ` Chandan Babu R
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=20201103150642.2032284-4-chandanrlinux@gmail.com \
--to=chandanrlinux@gmail.com \
--cc=allison.henderson@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-xfs@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