From: Eric Sandeen <sandeen@redhat.com>
To: fstests <fstests@vger.kernel.org>
Subject: [PATCH] xfs/270: allow corrupted xfs_db write
Date: Tue, 25 Sep 2018 13:16:16 -0500 [thread overview]
Message-ID: <a2a62573-efd2-f3f6-b986-029bb691372d@redhat.com> (raw)
Upcoming verifiers treat the unknown ro_compat flag written via xfs_db
as corruption, so use the -d flag to allow it, and filter our the
resulting informational message.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/tests/xfs/270 b/tests/xfs/270
index d5c8df19..da66bc33 100755
--- a/tests/xfs/270
+++ b/tests/xfs/270
@@ -44,7 +44,8 @@ _scratch_mkfs_xfs >>$seqres.full 2>&1
# set the highest bit of features_ro_compat, use it as an unknown
# feature bit. If one day this bit become known feature, please
# change this case.
-$XFS_DB_PROG -x -c "sb 0" -c "write features_ro_compat $((2**31))" $SCRATCH_DEV
+$XFS_DB_PROG -x -c "sb 0" -c "write -d features_ro_compat $((2**31))" \
+ $SCRATCH_DEV | grep -v "Allowing write of corrupted data"
# rw mount with unknown ro-compat feature should fail
echo "rw mount test"
next reply other threads:[~2018-09-26 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 18:16 Eric Sandeen [this message]
2018-09-26 0:13 ` [PATCH] xfs/270: allow corrupted xfs_db write 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=a2a62573-efd2-f3f6-b986-029bb691372d@redhat.com \
--to=sandeen@redhat.com \
--cc=fstests@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.