From: Theodore Ts'o <tytso@mit.edu>
To: Xiong Zhou <xzhou@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: Ext4 new shutdown ioctl fails generic/04{4,5,6}
Date: Tue, 28 Feb 2017 00:13:37 -0500 [thread overview]
Message-ID: <20170228051337.lxmiiz7jzhojmagz@thunk.org> (raw)
In-Reply-To: <20170228032556.dc5d26cldwku4puw@XZHOUW.usersys.redhat.com>
On Tue, Feb 28, 2017 at 11:25:56AM +0800, Xiong Zhou wrote:
>
> On latest Linus tree, xfstests generic/04{4,5,6} fails.
Yes, that's known issue. generic/04[456] were originally XFS specific
tests, and they have have assumptions about the implementation of the
underlying file system.
We have a few of those at the moment in kvm-xfstests/gce-xfstests's
exclude file:
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests/test-appliance/files/root/fs/ext4/exclude
# generic/042 and generic/392 are failing because ext4 forces the
# resolution of all delayed allocation writes before allowing the
# punch operation to proceed. We probably want to see if we can avoid
# this for the future, but what ext4 is doing is legal, so just skip
# the test for now
generic/042
generic/392
# generic/04[456] tests how truncate and delayed allocation works
# ext4 uses the data=ordered to avoid exposing stale data, and
# so it uses a different mechanism than xfs. So these tests will fail
generic/044
generic/045
generic/046
# generic/223 tests file alignment, which works on ext4 only by
# accident because we're not RAID stripe aware yet, and works at all
# because we have bias towards aligning on power-of-two block numbers.
# It is a flaky test for some configurations, so skip it.
generic/223
# ext4/304 fails for all configurations, and this appears to be at
# test or fio bug.
#
ext4/304
Cheers,
- Ted
prev parent reply other threads:[~2017-02-28 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 3:25 Ext4 new shutdown ioctl fails generic/04{4,5,6} Xiong Zhou
2017-02-28 5:13 ` Theodore Ts'o [this message]
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=20170228051337.lxmiiz7jzhojmagz@thunk.org \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xzhou@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