From: Eryu Guan <eguan@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: [4.14-rc1 bug] fstests generic/441 failure on ext2
Date: Mon, 18 Sep 2017 19:23:12 +0800 [thread overview]
Message-ID: <20170918112312.GN8034@eguan.usersys.redhat.com> (raw)
Hi all,
With ext2 driven by ext4 module (or ext4 without journal, I haven't
tested ext2 module, but I guess the result is the same), v4.14-rc1
kernel starts to fail fstests generic/441 as:
+First fsync after reopen of fd[0] failed: Input/output error
git bisect shows that this is uncovered by commit ffb959bbdf92 ("mm:
remove optimizations based on i_size in mapping writeback waits"), which
removed (i_size == 0) check in filemap_fdatawait().
I say "uncovered" because test fails with 4.13 kernel too if we re-open
the test file without O_TRUNC flag in src/fsync-err.c (so file size is
not zero, and fails the i_size == 0 check).
The EIO was returned by sync_inode_metadata() in __generic_file_fsync(),
the call trace is like:
do_fsync
vfs_fsync_range
ext4_sync_file
__generic_file_fsync
sync_inode_metadata
writeback_single_inode
__writeback_single_inode
filemap_fdatawait => EIO here
Thanks,
Eryu
next reply other threads:[~2017-09-18 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 11:23 Eryu Guan [this message]
2017-09-18 12:10 ` [4.14-rc1 bug] fstests generic/441 failure on ext2 Jeff Layton
2017-09-19 14:57 ` Jan Kara
2017-09-19 15:09 ` Jeff Layton
2017-09-20 11:12 ` Jan Kara
2017-09-22 13:33 ` [PATCH] mm: have filemap_check_and_advance_wb_err clear AS_EIO/AS_ENOSPC Jeff Layton
2017-09-25 8:17 ` Jan Kara
2017-09-25 19:53 ` Jeff Layton
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=20170918112312.GN8034@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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 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).