From: Chandan Babu R <chandanrlinux@gmail.com>
To: fstests@vger.kernel.org
Cc: Chandan Babu R <chandanrlinux@gmail.com>,
linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: [PATCH V2 04/11] xfs: Check for extent overflow when punching a hole
Date: Sat, 21 Nov 2020 13:53:25 +0530 [thread overview]
Message-ID: <20201121082332.89739-5-chandanrlinux@gmail.com> (raw)
In-Reply-To: <20201121082332.89739-1-chandanrlinux@gmail.com>
This test verifies that XFS does not cause inode fork's extent count to
overflow when punching out an extent.
Signed-off-by: Chandan Babu R <chandanrlinux@gmail.com>
---
tests/xfs/524 | 84 +++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/524.out | 19 +++++++++++
tests/xfs/group | 1 +
3 files changed, 104 insertions(+)
create mode 100755 tests/xfs/524
create mode 100644 tests/xfs/524.out
diff --git a/tests/xfs/524 b/tests/xfs/524
new file mode 100755
index 00000000..ba0b1a3b
--- /dev/null
+++ b/tests/xfs/524
@@ -0,0 +1,84 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2020 Chandan Babu R. All Rights Reserved.
+#
+# FS QA Test 524
+#
+# Verify that XFS does not cause inode fork's extent count to overflow when
+# punching out an extent.
+seq=`basename $0`
+seqres=$RESULT_DIR/$seq
+echo "QA output created by $seq"
+
+here=`pwd`
+tmp=/tmp/$$
+status=1 # failure is the default!
+trap "_cleanup; exit \$status" 0 1 2 3 15
+
+_cleanup()
+{
+ cd /
+ rm -f $tmp.*
+}
+
+# get standard environment, filters and checks
+. ./common/rc
+. ./common/filter
+. ./common/inject
+
+# remove previous $seqres.full before test
+rm -f $seqres.full
+
+# real QA test starts here
+
+_supported_fs xfs
+_require_scratch
+_require_xfs_debug
+_require_xfs_io_command "fpunch"
+_require_xfs_io_command "finsert"
+_require_xfs_io_command "fcollapse"
+_require_xfs_io_command "fzero"
+_require_xfs_io_error_injection "reduce_max_iextents"
+
+echo "Format and mount fs"
+_scratch_mkfs >> $seqres.full
+_scratch_mount >> $seqres.full
+
+bsize=$(_get_file_block_size $SCRATCH_MNT)
+nr_blks=80
+
+testfile=$SCRATCH_MNT/testfile
+
+echo "Inject reduce_max_iextents error tag"
+_scratch_inject_error reduce_max_iextents 1
+
+for op in fpunch finsert fcollapse fzero; do
+ echo "* $op regular file"
+
+ echo "Create \$testfile"
+ $XFS_IO_PROG -f -s \
+ -c "pwrite -b $((nr_blks * bsize)) 0 $((nr_blks * bsize))" \
+ $testfile >> $seqres.full
+
+ echo "$op alternating blocks"
+ for i in $(seq 1 2 $((nr_blks - 1))); do
+ $XFS_IO_PROG -f -c "$op $((i * bsize)) $bsize" $testfile \
+ >> $seqres.full 2>&1
+ [[ $? != 0 ]] && break
+ done
+
+ echo "Verify \$testfile's extent count"
+
+ nextents=$($XFS_IO_PROG -f -c 'stat' $testfile | grep -i nextents)
+ nextents=${nextents##fsxattr.nextents = }
+ if (( $nextents > 35 )); then
+ echo "Extent count overflow check failed: nextents = $nextents"
+ exit 1
+ fi
+
+ rm $testfile
+done
+
+# success, all done
+status=0
+exit
diff --git a/tests/xfs/524.out b/tests/xfs/524.out
new file mode 100644
index 00000000..a957f9c7
--- /dev/null
+++ b/tests/xfs/524.out
@@ -0,0 +1,19 @@
+QA output created by 524
+Format and mount fs
+Inject reduce_max_iextents error tag
+* fpunch regular file
+Create $testfile
+fpunch alternating blocks
+Verify $testfile's extent count
+* finsert regular file
+Create $testfile
+finsert alternating blocks
+Verify $testfile's extent count
+* fcollapse regular file
+Create $testfile
+fcollapse alternating blocks
+Verify $testfile's extent count
+* fzero regular file
+Create $testfile
+fzero alternating blocks
+Verify $testfile's extent count
diff --git a/tests/xfs/group b/tests/xfs/group
index b375a94c..7031cabf 100644
--- a/tests/xfs/group
+++ b/tests/xfs/group
@@ -521,6 +521,7 @@
521 auto quick realtime growfs
522 auto quick quota
523 auto quick realtime growfs
+524 auto quick punch zero insert collapse
758 auto quick rw attr realtime
759 auto quick rw realtime
760 auto quick rw collapse punch insert zero prealloc
--
2.29.2
next prev parent reply other threads:[~2020-11-21 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 8:23 [PATCH V2 00/11] xfs: Tests to check for inode fork extent count overflow detection Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 01/11] common/xfs: Add a helper to get an inode fork's extent count Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 03/11] xfs: Check for extent overflow when growing realtime bitmap/summary inodes Chandan Babu R
2020-11-21 8:23 ` Chandan Babu R [this message]
2020-11-21 8:23 ` [PATCH V2 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 11/11] xfs: Stress test with with bmap_alloc_minlen_extent error tag enabled 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=20201121082332.89739-5-chandanrlinux@gmail.com \
--to=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).