From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: guaneryu@gmail.com, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
fstests@vger.kernel.org
Subject: [PATCH 5/6] xfs/288: shut up verifier error
Date: Thu, 04 Oct 2018 17:19:39 -0700 [thread overview]
Message-ID: <153869877948.26648.4238107405182797711.stgit@magnolia> (raw)
In-Reply-To: <153869874763.26648.516233620615833277.stgit@magnolia>
From: Darrick J. Wong <darrick.wong@oracle.com>
Ignore the verifier errors when we fuzz hdr.count to zero.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
tests/xfs/288 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/288 b/tests/xfs/288
index c6821909..13ba3057 100755
--- a/tests/xfs/288
+++ b/tests/xfs/288
@@ -62,7 +62,7 @@ _scratch_xfs_set_metadata_field "hdr.count" "0" \
# verify current xfs_db write command can set hdr.count to 0. Old xfsprogs
# can't do that on v5 filesystems.
count=$(_scratch_xfs_get_metadata_field "hdr.count" \
- "inode $inum" "ablock 0")
+ "inode $inum" "ablock 0" 2> /dev/null)
if [ "$count" != "0" ]; then
_notrun "xfs_db can't set attr hdr.count to 0"
fi
next prev parent reply other threads:[~2018-10-05 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 0:19 [PATCH 0/6] fstests: fixes and new tests Darrick J. Wong
2018-10-05 0:19 ` [PATCH 1/6] generic: add bfoster's alternate reproducer Darrick J. Wong
2018-10-05 0:19 ` [PATCH 2/6] xfs: test mount time summary counter check and fix Darrick J. Wong
2018-10-05 0:19 ` [PATCH 3/6] xfs/189: skip 'barrier' mount option test on newer kernels Darrick J. Wong
2018-10-05 0:19 ` [PATCH 4/6] xfs/270: use _scratch_xfs_set_metadata_field to fuzz rocompat bits Darrick J. Wong
2018-10-05 6:54 ` Xiao Yang
2018-10-05 6:54 ` Xiao Yang
2018-10-05 0:19 ` Darrick J. Wong [this message]
2018-10-05 0:19 ` [PATCH 6/6] generic: test reflink side effects Darrick J. Wong
2018-10-14 15:40 ` Eryu Guan
2018-10-15 18:57 ` Darrick J. Wong
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=153869877948.26648.4238107405182797711.stgit@magnolia \
--to=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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.