From: Eryu Guan <eguan@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, mhocko@suse.com
Subject: Re: [BUG 4.10-rc7] sb_fdblocks inconsistency in xfs/297 test
Date: Fri, 10 Feb 2017 12:20:40 +0800 [thread overview]
Message-ID: <20170210042040.GA21408@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170210035348.GA7075@eguan.usersys.redhat.com>
On Fri, Feb 10, 2017 at 11:53:48AM +0800, Eryu Guan wrote:
> Hi,
>
> I was testing 4.10-rc7 kernel and noticed that xfs_repair reported XFS
> corruption after fstests xfs/297 test. This didn't happen with 4.10-rc6
Seems generic/269 reproduces it easily too. I also saw xfs/167 fail on
ppc64 host because of this issue, but rarely.
Thanks,
Eryu
next prev parent reply other threads:[~2017-02-10 4:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 3:53 [BUG 4.10-rc7] sb_fdblocks inconsistency in xfs/297 test Eryu Guan
2017-02-10 4:20 ` Eryu Guan [this message]
2017-02-10 7:14 ` Michal Hocko
2017-02-10 8:02 ` Michal Hocko
2017-02-10 9:31 ` Michal Hocko
2017-02-11 6:02 ` Eryu Guan
2017-02-11 6:33 ` Michal Hocko
2017-02-20 14:25 ` Michal Hocko
2017-02-20 14:58 ` Brian Foster
2017-02-21 4:14 ` Eryu Guan
2017-02-21 8:13 ` Michal Hocko
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=20170210042040.GA21408@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhocko@suse.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;
as well as URLs for NNTP newsgroup(s).