From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCH 2/2] xfs/507: add test to auto group
Date: Mon, 11 Apr 2022 15:54:28 -0700 [thread overview]
Message-ID: <164971766805.169895.12082898167045363438.stgit@magnolia> (raw)
In-Reply-To: <164971765670.169895.10730350919455923432.stgit@magnolia>
From: Darrick J. Wong <djwong@kernel.org>
Add this regression test to the auto group now that it's been quite a
while since the fix patches went upstream.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
tests/xfs/507 | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tests/xfs/507 b/tests/xfs/507
index aa3d8eeb..b9c9ab29 100755
--- a/tests/xfs/507
+++ b/tests/xfs/507
@@ -4,13 +4,17 @@
#
# FS QA Test No. 507
#
+# Regression test for kernel commit:
+#
+# 394aafdc15da ("xfs: widen inode delalloc block counter to 64-bits")
+#
# Try to overflow i_delayed_blks by setting the largest cowextsize hint
# possible, creating a sparse file with a single byte every cowextsize bytes,
# reflinking it, and retouching every written byte to see if we can create
# enough speculative COW reservations to overflow i_delayed_blks.
#
. ./common/preamble
-_begin_fstest clone
+_begin_fstest auto clone
_register_cleanup "_cleanup" BUS
next prev parent reply other threads:[~2022-04-11 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 22:54 [PATCHSET 0/2] fstests: random fixes Darrick J. Wong
2022-04-11 22:54 ` [PATCH 1/2] xfs/187: don't rely on FSCOUNTS for free space data Darrick J. Wong
2022-04-12 8:47 ` Zorro Lang
2022-04-12 17:11 ` Darrick J. Wong
2022-04-13 18:23 ` Zorro Lang
2022-04-11 22:54 ` Darrick J. Wong [this message]
2022-04-12 8:47 ` [PATCH 2/2] xfs/507: add test to auto group 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=164971766805.169895.12082898167045363438.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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).