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 v3 2/2] ext4: set 256 blocks in a block group then apply io pressure
Date: Wed, 13 Jul 2022 17:28:59 +0800 [thread overview]
Message-ID: <20220713092859.3881376-3-sunke32@huawei.com> (raw)
In-Reply-To: <20220713092859.3881376-1-sunke32@huawei.com>
Set 256 blocks in a block group, then inject I/O pressure, it will
trigger off kernel BUG in ext4_mb_mark_diskspace_used.
Regression test for commit a08f789d2ab5 ext4: fix bug_on
ext4_mb_use_inode_pa.
Signed-off-by: Sun Ke <sunke32@huawei.com>
---
tests/ext4/058 | 33 +++++++++++++++++++++++++++++++++
tests/ext4/058.out | 2 ++
2 files changed, 35 insertions(+)
create mode 100755 tests/ext4/058
create mode 100644 tests/ext4/058.out
diff --git a/tests/ext4/058 b/tests/ext4/058
new file mode 100755
index 00000000..ddc96f30
--- /dev/null
+++ b/tests/ext4/058
@@ -0,0 +1,33 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2022 HUAWEI. All Rights Reserved.
+#
+# FS QA Test 058
+#
+# Set 256 blocks in a block group, then inject I/O pressure,
+# it will trigger off kernel BUG in ext4_mb_mark_diskspace_used
+#
+# Regression test for commit
+# a08f789d2ab5 ext4: fix bug_on ext4_mb_use_inode_pa
+#
+. ./common/preamble
+_begin_fstest auto quick
+
+# real QA test starts here
+
+_supported_fs ext4
+_fixed_by_kernel_commit a08f789d2ab5 \
+ "ext4: fix bug_on ext4_mb_use_inode_pa"
+_require_scratch
+
+# set 256 blocks in a block group
+_scratch_mkfs -g 256 >> $seqres.full 2>&1 || _fail "mkfs failed"
+_scratch_mount
+
+$FSSTRESS_PROG -d $SCRATCH_MNT/stress -n 1000 >> $seqres.full 2>&1
+
+echo "Silence is golden"
+
+# success, all done
+status=0
+exit
diff --git a/tests/ext4/058.out b/tests/ext4/058.out
new file mode 100644
index 00000000..fb5ca60b
--- /dev/null
+++ b/tests/ext4/058.out
@@ -0,0 +1,2 @@
+QA output created by 058
+Silence is golden
--
2.13.6
next prev parent reply other threads:[~2022-07-13 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:28 [PATCH v3 0/2] two regression tests for ext4 Sun Ke
2022-07-13 9:28 ` [PATCH v3 1/2] ext4: resize fs after resize_inode without e2fsck Sun Ke
2022-07-14 15:46 ` Zorro Lang
2022-07-14 22:00 ` Theodore Ts'o
2022-07-15 18:08 ` Zorro Lang
2022-07-21 3:24 ` Sun Ke
2022-07-22 8:16 ` Sun Ke
2022-07-22 11:51 ` Theodore Ts'o
2022-07-22 15:11 ` Zorro Lang
2022-07-22 16:36 ` Theodore Ts'o
2022-07-13 9:28 ` Sun Ke [this message]
2022-07-14 16:02 ` [PATCH v3 2/2] ext4: set 256 blocks in a block group then apply io pressure Zorro Lang
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=20220713092859.3881376-3-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