From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: guaneryu@gmail.com, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/5] fstests: fix various problems
Date: Tue, 18 Dec 2018 12:35:43 -0800 [thread overview]
Message-ID: <154516534392.31115.7010578395334646479.stgit@magnolia> (raw)
Hi all,
Here are some fixes for various fstests failures.
Patch 1 fixes a weird porting problem in xfs/111 when it was converted
to use xfs_fsr.
Patch 2 fixes xfs/123 to eliminate a corruption error in the golden
output on 1k v5 filesystems.
Patch 3 is a revised version of a previous patch that works around the
fact that mounting xfs with quotas requires a writable block device even
for a ro mount, which leads to a slightly different error message from
the mount call.
Patch 4 adds a new test to look for forgotten TRACE_DEFINE_ENUM wrappers
for xfs enums that are used as part of __print_symbolic() calls in the
trace points.
Patch 5 is the same old patch that filters v5 mount options out of
MOUNT_OPTIONS when the test formats a v4 filesystem, rather than letting
the test fail due to bad mount options.
--D
next reply other threads:[~2018-12-18 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 20:35 Darrick J. Wong [this message]
2018-12-18 20:35 ` [PATCH 1/5] xfs/111: fix golden output Darrick J. Wong
2018-12-18 20:35 ` [PATCH 2/5] xfs/123: fix remote symlink block size calculation Darrick J. Wong
2018-12-18 20:36 ` [PATCH 3/5] generic/050: fix ro blockdev mount of xfs with quota Darrick J. Wong
2018-12-18 20:36 ` [PATCH 4/5] xfs: look for stringified constants in ftrace formats Darrick J. Wong
2018-12-18 20:36 ` [PATCH 5/5] xfs: filter out mount options that don't work on v4 filesystems 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=154516534392.31115.7010578395334646479.stgit@magnolia \
--to=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--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.