From: Lukas Czerner <lczerner@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Lukas Czerner <lczerner@redhat.com>
Subject: [PATCH v3 2/2] generic: test bug when zero range is crossing isize within single block
Date: Mon, 27 Apr 2015 16:33:20 +0200 [thread overview]
Message-ID: <1430145200-20230-2-git-send-email-lczerner@redhat.com> (raw)
In-Reply-To: <1430145200-20230-1-git-send-email-lczerner@redhat.com>
Exercise the situation that cause ext4 to BUG_ON() when we use
zero range to zero a range which starts within the isize but ends
past the isize but still in the same block. This particular problem
has only been seen on systems with page_size > block_size.
This tests exercises the problem fixed in kernel with commit
0f2af21aae11972fa924374ddcf52e88347cf5a8
ext4: Allocate entire range in zero range
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
---
tests/generic/084 | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/084.out | 1 +
tests/generic/group | 1 +
3 files changed, 62 insertions(+)
create mode 100755 tests/generic/084
create mode 100644 tests/generic/084.out
diff --git a/tests/generic/084 b/tests/generic/084
new file mode 100755
index 0000000..5066b14
--- /dev/null
+++ b/tests/generic/084
@@ -0,0 +1,60 @@
+#! /bin/bash
+# FS QA Test 084
+#
+# Exercise the situation that cause ext4 to BUG_ON() when we use
+# zero range to zero a range which starts within the isize but ends
+# past the isize but still in the same block. This particular problem
+# has only been seen on systems with page_size > block_size.
+#
+#-----------------------------------------------------------------------
+# Copyright (c) 2015 Red Hat, Inc., Lukas Czerner <lczerner@redhat.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"
+
+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
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs generic
+_supported_os IRIX Linux
+_require_test
+_require_xfs_io_command "fzero"
+
+testfile=$TEST_DIR/$seq.$$
+
+$XFS_IO_PROG -f -c "pwrite 4096 512" -c "fzero 4351 512" $testfile > $seqres.full 2>&1
+
+# success, all done
+status=0
+exit
diff --git a/tests/generic/084.out b/tests/generic/084.out
new file mode 100644
index 0000000..d0aa380
--- /dev/null
+++ b/tests/generic/084.out
@@ -0,0 +1 @@
+QA output created by 084
diff --git a/tests/generic/group b/tests/generic/group
index c6ea3d8..6cb7dc3 100644
--- a/tests/generic/group
+++ b/tests/generic/group
@@ -86,6 +86,7 @@
081 auto quick
082 auto prealloc preallocrw quick
083 rw auto enospc stress
+084 auto prealloc quick
088 perms auto quick
089 metadata auto
091 rw auto quick
--
1.8.3.1
prev parent reply other threads:[~2015-04-27 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 14:33 [PATCH v3 1/2] generic: test data corruption on ext4 caused by written/delayed extent Lukas Czerner
2015-04-27 14:33 ` Lukas Czerner [this message]
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=1430145200-20230-2-git-send-email-lczerner@redhat.com \
--to=lczerner@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@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).