From: Sun Ke <sunke32@huawei.com>
To: <fstests@vger.kernel.org>
Cc: <zlang@kernel.org>, <linux-ext4@vger.kernel.org>, <sunke32@huawei.com>
Subject: [PATCH 1/2] ext4/057: resize fs after resize_inode without e2fsck
Date: Thu, 7 Jul 2022 21:59:16 +0800 [thread overview]
Message-ID: <20220707135917.373342-2-sunke32@huawei.com> (raw)
In-Reply-To: <20220707135917.373342-1-sunke32@huawei.com>
Forget to run requested e2fsck after resize_inode, then resize fs, it
will trigger off null pointer.
Regression test for commit b55c3cd102a6 ext4: add reserved GDT blocks
check
Signed-off-by: Sun Ke <sunke32@huawei.com>
---
tests/ext4/057 | 41 +++++++++++++++++++++++++++++++++++++++++
tests/ext4/057.out | 2 ++
2 files changed, 43 insertions(+)
create mode 100755 tests/ext4/057
create mode 100644 tests/ext4/057.out
diff --git a/tests/ext4/057 b/tests/ext4/057
new file mode 100755
index 00000000..dacc14be
--- /dev/null
+++ b/tests/ext4/057
@@ -0,0 +1,41 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2022 HUAWEI. All Rights Reserved.
+#
+# FS QA Test 057
+#
+# Forget to run requested e2fsck after resize_inode, then resize fs,
+# it will trigger off null pointer.
+#
+# Regression test for commit
+# b55c3cd102a6 ext4: add reserved GDT blocks check
+#
+. ./common/preamble
+_begin_fstest auto
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs ext4
+_require_scratch
+_require_command "$TUNE2FS_PROG" tune2fs
+_require_command "$RESIZE2FS_PROG" resize2
+
+
+# set fs size 3G
+dev_size=$((3 * 1024 * 1024 * 1024))
+_scratch_mkfs_sized $dev_size >/dev/null 2>&1
+
+# forget to run requested e2fsck after resize_inode
+$TUNE2FS_PROG -O ^resize_inode $SCRATCH_DEV >/dev/null 2>&1
+
+_scratch_mount
+
+# resize fs from 3G to 8G
+$RESIZE2FS_PROG $SCRATCH_DEV 8G >/dev/null 2>&1
+
+echo "Silence is golden"
+
+# success, all done
+status=0
+exit
diff --git a/tests/ext4/057.out b/tests/ext4/057.out
new file mode 100644
index 00000000..185023c7
--- /dev/null
+++ b/tests/ext4/057.out
@@ -0,0 +1,2 @@
+QA output created by 057
+Silence is golden
--
2.13.6
next prev parent reply other threads:[~2022-07-07 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:59 [PATCH 0/2] two regression tests for ext4 Sun Ke
2022-07-07 13:59 ` Sun Ke [this message]
2022-07-07 15:00 ` [PATCH 1/2] ext4/057: resize fs after resize_inode without e2fsck Zorro Lang
2022-07-07 13:59 ` [PATCH 2/2] ext4/058: set 256 blocks in a block group Set 256 blocks in a block group Sun Ke
2022-07-07 15:18 ` Zorro Lang
2022-07-08 11:03 ` Sun Ke
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=20220707135917.373342-2-sunke32@huawei.com \
--to=sunke32@huawei.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=zlang@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