new file mode 100755
@@ -0,0 +1,102 @@
+#! /bin/bash
+# FS QA Test No. btrfs/087
+#
+# Test btrfs file range cloning with the same file as a source and destination.
+#
+# This tests a specific scenario where the extent layout of the file confused
+# the clone ioctl implementation making it return -EEXIST to userspace.
+# This issue was fixed by the following linux kernel patch:
+#
+# Btrfs: fix range cloning when same inode used as source and destination
+#
+#-----------------------------------------------------------------------
+# Copyright (C) 2015 SUSE Linux Products GmbH. All Rights Reserved.
+# Author: Filipe Manana <fdmanana@suse.com>
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it would be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write the Free Software Foundation,
+# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+#-----------------------------------------------------------------------
+#
+
+seq=`basename $0`
+seqres=$RESULT_DIR/$seq
+echo "QA output created by $seq"
+
+tmp=/tmp/$$
+status=1 # failure is the default!
+trap "_cleanup; exit \$status" 0 1 2 3 15
+
+_cleanup()
+{
+ rm -f $tmp.*
+}
+
+# get standard environment, filters and checks
+. ./common/rc
+. ./common/filter
+
+# real QA test starts here
+_supported_fs btrfs
+_supported_os Linux
+_require_scratch
+_require_cloner
+_need_to_be_root
+
+rm -f $seqres.full
+
+# Create a file with an extent layout that confused the btrfs clone ioctl
+# implementation. The first extent item that is cloned by the second call
+# to the cloner program will have only a trailing part of it referenced by
+# a new extent item, since the source offset starts in the middle of that
+# extent. This confused the clone ioctl because after inserting this new
+# extent item it would immediately after process it again thinking it
+# corresponded to an extent that existed before - this made it attempt to
+# insert a duplicated extent item pointing to the same extent again, which
+# made it return an -EEXIST error to userspace and turn the filesystem to
+# readonly mode (since the current transaction got aborted).
+test_clone()
+{
+ local bs=$1
+
+ $XFS_IO_PROG -f -c "pwrite -S 0xaa $(($bs * 2)) $(($bs * 2))" \
+ $SCRATCH_MNT/foo | _filter_xfs_io
+
+ $CLONER_PROG -s $((3 * $bs)) -d $((267 * $bs)) -l 0 $SCRATCH_MNT/foo \
+ $SCRATCH_MNT/foo
+ $CLONER_PROG -s $((217 * $bs)) -d $((95 * $bs)) -l 0 $SCRATCH_MNT/foo \
+ $SCRATCH_MNT/foo
+
+ echo "File content after clone operations:"
+ od -t x1 $SCRATCH_MNT/foo
+}
+
+# Make sure the test passes offsets and lengths to the btrfs clone ioctl that
+# are multiples of the fs block size. Currently the block size on btrfs must
+# be a multiple of the page size, so use a 64Kb fs block size in order to be
+# able to test on every platform supported by linux.
+bs=$((64 * 1024))
+
+echo "Testing without the no-holes feature"
+_scratch_mkfs "-O ^no-holes -l $bs" >>$seqres.full 2>&1
+_scratch_mount
+test_clone $bs
+_check_scratch_fs
+
+echo "Testing with the no-holes feature"
+_scratch_unmount
+_scratch_mkfs "-O no-holes -l $bs" >>$seqres.full 2>&1
+_scratch_mount
+test_clone $bs
+
+status=0
+exit
new file mode 100644
@@ -0,0 +1,35 @@
+QA output created by 087
+Testing without the no-holes feature
+wrote 131072/131072 bytes at offset 131072
+XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+File content after clone operations:
+0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+0400000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+1000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+44200000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+44400000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+102600000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+103000000
+Testing with the no-holes feature
+wrote 131072/131072 bytes at offset 131072
+XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+File content after clone operations:
+0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+0400000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+1000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+44200000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+44400000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+*
+102600000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
+*
+103000000
@@ -89,3 +89,4 @@
084 auto quick send
085 auto quick send
086 auto quick clone
+087 auto quick clone
Test btrfs file range cloning with the same file as a source and destination. This tests a specific scenario where the extent layout of the file confused the clone ioctl implementation making it return -EEXIST to userspace. This issue was fixed by the following linux kernel patch: Btrfs: fix range cloning when same inode used as source and destination Signed-off-by: Filipe Manana <fdmanana@suse.com> --- tests/btrfs/087 | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/btrfs/087.out | 35 ++++++++++++++++++ tests/btrfs/group | 1 + 3 files changed, 138 insertions(+) create mode 100755 tests/btrfs/087 create mode 100644 tests/btrfs/087.out