From: Shiyang Ruan <ruansy.fnst@fujitsu.com>
To: <fstests@vger.kernel.org>
Subject: [PATCH 05/13] generic: add mmap CoW test for delalloc&destination extents
Date: Thu, 11 Nov 2021 16:50:58 +0800 [thread overview]
Message-ID: <20211111085106.937684-6-ruansy.fnst@fujitsu.com> (raw)
In-Reply-To: <20211111085106.937684-1-ruansy.fnst@fujitsu.com>
Ensuring that copy on write in mmap mode works when the CoW range originally
covers multiple extents, some delalloc, some not.
(MMAP version of generic/195,194)
Also, add a check to make sure the delalloc block accutally exists.
Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>
---
common/reflink | 3 +++
tests/generic/913 | 61 +++++++++++++++++++++++++++++++++++++++++++
tests/generic/913.out | 12 +++++++++
3 files changed, 76 insertions(+)
create mode 100755 tests/generic/913
create mode 100644 tests/generic/913.out
diff --git a/common/reflink b/common/reflink
index ee60398e..38210673 100644
--- a/common/reflink
+++ b/common/reflink
@@ -296,6 +296,9 @@ _weave_reflink_holes_delalloc() {
_pwrite_byte 0x62 $((blksz * i)) $blksz $dfile
_pwrite_byte 0x62 $((blksz * i)) $blksz $dfile.chk
done
+ # make sure we actually got delalloc block
+ $FILEFRAG_PROG -v $dfile 2>&1 | grep -q delalloc || \
+ _notrun "test requires delayed allocation writes"
}
# Create a file of interleaved regular blocks and reflinked blocks
diff --git a/tests/generic/913 b/tests/generic/913
new file mode 100755
index 00000000..c02886fa
--- /dev/null
+++ b/tests/generic/913
@@ -0,0 +1,61 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+#
+# FS QA Test No. xxx
+#
+# Ensuring that copy on write in mmap mode works when the CoW
+# range originally covers multiple extents, some delalloc, some not.
+# (MMAP version of generic/195,194)
+# - Create a file.
+# - Reflink the odd blocks of the first file into the second file.
+# - Buffered write the even blocks of the second file.
+# - mmap CoW across the halfway mark, starting with the unwritten extent.
+# - Check that the files are now different where we say they're different.
+#
+. ./common/preamble
+_begin_fstest auto quick clone
+
+# Import common functions.
+. ./common/filter
+. ./common/reflink
+
+# real QA test starts here
+_require_scratch_reflink
+_require_xfs_io_command "falloc"
+
+echo "Format and mount"
+_scratch_mkfs > $seqres.full 2>&1
+_scratch_mount >> $seqres.full 2>&1
+
+testdir=$SCRATCH_MNT/test-$seq
+mkdir $testdir
+
+echo "Create the original files"
+blksz=65536
+nr=64
+filesize=$((blksz * nr))
+_weave_reflink_holes $blksz $nr $testdir/file1 $testdir/file3 >> $seqres.full
+_scratch_cycle_mount
+
+echo "Compare files"
+md5sum $testdir/file1 | _filter_scratch
+md5sum $testdir/file3 | _filter_scratch
+md5sum $testdir/file3.chk | _filter_scratch
+
+echo "mmap CoW across the transition"
+cowoff=$((filesize / 4))
+cowsz=$((filesize / 2))
+_weave_reflink_holes_delalloc $blksz $nr $testdir/file3 >> $seqres.full
+mmapsz=$((cowoff + cowsz))
+_mwrite_byte 0x63 $cowoff $cowsz $mmapsz $testdir/file3 >> $seqres.full
+_mwrite_byte 0x63 $cowoff $cowsz $mmapsz $testdir/file3.chk >> $seqres.full
+_scratch_cycle_mount
+
+echo "Compare files"
+md5sum $testdir/file1 | _filter_scratch
+md5sum $testdir/file3 | _filter_scratch
+md5sum $testdir/file3.chk | _filter_scratch
+
+# success, all done
+status=0
+exit
diff --git a/tests/generic/913.out b/tests/generic/913.out
new file mode 100644
index 00000000..1f08400e
--- /dev/null
+++ b/tests/generic/913.out
@@ -0,0 +1,12 @@
+QA output created by 913
+Format and mount
+Create the original files
+Compare files
+bdbcf02ee0aa977795a79d25fcfdccb1 SCRATCH_MNT/test-913/file1
+fa50dba51826899c372464a153cb2117 SCRATCH_MNT/test-913/file3
+fa50dba51826899c372464a153cb2117 SCRATCH_MNT/test-913/file3.chk
+mmap CoW across the transition
+Compare files
+bdbcf02ee0aa977795a79d25fcfdccb1 SCRATCH_MNT/test-913/file1
+55968a95dfc0120df4e8485576514320 SCRATCH_MNT/test-913/file3
+55968a95dfc0120df4e8485576514320 SCRATCH_MNT/test-913/file3.chk
--
2.33.0
next prev parent reply other threads:[~2021-11-11 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 8:50 [PATCH 00/13] generic: add some mmap CoW tests Shiyang Ruan
2021-11-11 8:50 ` [PATCH 01/13] generic: add mmap CoW test for ranges of two shared files Shiyang Ruan
2021-11-11 8:50 ` [PATCH 02/13] generic: add mmap CoW test for regular&destination extents Shiyang Ruan
2021-11-11 8:50 ` [PATCH 03/13] generic: add mmap CoW test for unwritten&destination extents Shiyang Ruan
2021-11-11 8:50 ` [PATCH 04/13] generic: add mmap CoW test for holes&destination extents Shiyang Ruan
2021-11-11 8:50 ` Shiyang Ruan [this message]
2021-11-11 8:50 ` [PATCH 06/13] generic: add mmap CoW test for mixed&destination extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 07/13] generic: add mmap CoW test for regular&source extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 08/13] generic: add mmap CoW test for unwritten&source extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 09/13] generic: add mmap CoW test for holes&source extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 10/13] generic: add mmap CoW test for delalloc&source extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 11/13] generic: add buffered-io CoW test for mixed&source extents Shiyang Ruan
2021-11-11 8:51 ` [PATCH 12/13] generic: add direct-io " Shiyang Ruan
2021-11-11 8:51 ` [PATCH 13/13] generic: add mmap " Shiyang Ruan
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=20211111085106.937684-6-ruansy.fnst@fujitsu.com \
--to=ruansy.fnst@fujitsu.com \
--cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.