From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: XFS kernel BUG during generic/270 with v4.10
Date: Wed, 22 Feb 2017 12:39:59 -0700 [thread overview]
Message-ID: <20170222193959.GB29474@linux.intel.com> (raw)
In-Reply-To: <20170222191300.GA29474@linux.intel.com>
On Wed, Feb 22, 2017 at 12:13:00PM -0700, Ross Zwisler wrote:
> By running generic/270 in a loop on an XFS filesystem mounted with DAX I'm
> able to reliably generate the following kernel bug after a few (~10)
> iterations (output passed through kasan_symbolize.py):
A few other notes which I should have included in the original report:
1) I initially found this while testing Brian's fix for the WARN_ON I reported
with this same test [1].
2) After the initial failure I was able to reproduce the issue reliably on
v4.10. Based on 1) and 2) my guess is that this failure is independent of the
other issue that I reported and that Brian was trying to fix. They just
happen to show up with the same xfstest.
[1] https://www.spinics.net/lists/linux-xfs/msg04300.html
Thanks,
- Ross
next prev parent reply other threads:[~2017-02-22 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 19:13 XFS kernel BUG during generic/270 with v4.10 Ross Zwisler
2017-02-22 19:39 ` Ross Zwisler [this message]
2017-03-02 16:29 ` Brian Foster
2017-03-02 16:47 ` Darrick J. Wong
2017-03-02 17:13 ` Brian Foster
2017-03-02 17:28 ` Darrick J. Wong
2017-03-02 17:25 ` Eric Sandeen
2017-03-06 18:41 ` Ross Zwisler
2017-03-06 18:48 ` Darrick J. Wong
2017-03-07 14:32 ` Brian Foster
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=20170222193959.GB29474@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.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 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).