From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: [PATCH] Add regression test for clearing an xattr block
Date: Fri, 11 Apr 2008 10:57:04 -0500 [thread overview]
Message-ID: <47FF8A50.2030800@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]
I got burned by the bug at:
http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commitdiff;h=86bc90f4f11df090f86dc764a4ea2d6dd5c13ffe
so figured maybe a testcase was in order...
20/20 hindsight I guess!
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
tests/f_clear_xattr_block/expect.1 | 22 ++++++++++++++++++++++
tests/f_clear_xattr_block/expect.2 | 7 +++++++
tests/f_clear_xattr_block/name | 1 +
3 files changed, 30 insertions(+), 0 deletions(-)
create mode 100644 tests/f_clear_xattr_block/expect.1
create mode 100644 tests/f_clear_xattr_block/expect.2
create mode 100644 tests/f_clear_xattr_block/name
diff --git a/tests/f_clear_xattr_block/expect.1 b/tests/f_clear_xattr_block/expect.1
new file mode 100644
index 0000000..f9db73d
--- /dev/null
+++ b/tests/f_clear_xattr_block/expect.1
@@ -0,0 +1,22 @@
+Pass 1: Checking inodes, blocks, and sizes
+Inode 12 has a bad extended attribute block 1112. Clear? yes
+
+Inode 12, i_blocks is 2, should be 0. Fix? yes
+
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+Block bitmap differences: -1112
+Fix? yes
+
+Free blocks count wrong for group #0 (7079, counted=7080).
+Fix? yes
+
+Free blocks count wrong (7079, counted=7080).
+Fix? yes
+
+
+test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
+test_filesys: 12/256 files (8.3% non-contiguous), 1112/8192 blocks
+Exit status is 1
diff --git a/tests/f_clear_xattr_block/expect.2 b/tests/f_clear_xattr_block/expect.2
new file mode 100644
index 0000000..3312a76
--- /dev/null
+++ b/tests/f_clear_xattr_block/expect.2
@@ -0,0 +1,7 @@
+Pass 1: Checking inodes, blocks, and sizes
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+test_filesys: 12/256 files (8.3% non-contiguous), 1112/8192 blocks
+Exit status is 0
diff --git a/tests/f_clear_xattr_block/name b/tests/f_clear_xattr_block/name
new file mode 100644
index 0000000..9848acc
--- /dev/null
+++ b/tests/f_clear_xattr_block/name
@@ -0,0 +1 @@
+clearing xattr block with bad header magic
-- 1.5.4.1
[-- Attachment #2: image.gz --]
[-- Type: application/x-gzip, Size: 23712 bytes --]
next reply other threads:[~2008-04-11 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 15:57 Eric Sandeen [this message]
2008-04-14 3:27 ` [PATCH] Add regression test for clearing an xattr block Andreas Dilger
2008-04-14 13:46 ` Eric Sandeen
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=47FF8A50.2030800@redhat.com \
--to=sandeen@redhat.com \
--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 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.