From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <wagi@monom.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
Reinoud Koornstra <reinoudkoornstra@gmail.com>,
viro@zeniv.linux.org.uk, xfs@oss.sgi.com
Subject: Re: crash in xfs in current
Date: Tue, 7 Jun 2016 06:44:42 -0700 [thread overview]
Message-ID: <20160607134442.GA1803@infradead.org> (raw)
In-Reply-To: <48817b4c-26f4-5eb6-8a97-d8fa34fe7f6a@monom.org>
On Tue, Jun 07, 2016 at 12:52:39PM +0200, Daniel Wagner wrote:
> >> I try to reproduce it on 4.6. My steps do not always trigger the crash.
> >> So I can't be really sure if 4.6 doesn't show it, it does not happen.
> >
> > I have never been able to trigger this in 4.6 and it's my failsafe
> > reboot (4.6.0).
> > In 4.7-rc1 it's just a matter of time before I hit it.
> > I do a lot of transactions, using git, extraction of tar.xz etc normally.
>
> This rings a bell. I though the lockperf tests triggered it. Before I
> compiled a new kernel I did a 'git checkout' step.
Thanks for testing this to both of you. Can you try to build a kernel
from git commit 555b67e4e729ca544bb4028ab12e532c68b70ddb - this is the
XFS pull request that Dave sent to Linux for Linux 4.7-rc, so it has
all the XFS changes relative to 4.6, but none of the others like the VFS
changes.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-07 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 1:43 crash in xfs in current Reinoud Koornstra
2016-06-07 4:39 ` Eric Sandeen
2016-06-07 6:27 ` Christoph Hellwig
2016-06-07 7:51 ` Daniel Wagner
2016-06-07 8:09 ` Reinoud Koornstra
2016-06-07 10:52 ` Daniel Wagner
2016-06-07 11:07 ` Reinoud Koornstra
2016-06-07 13:44 ` Christoph Hellwig [this message]
2016-06-07 23:40 ` Reinoud Koornstra
2016-06-08 4:16 ` Reinoud Koornstra
2016-06-08 4:40 ` Reinoud Koornstra
2016-06-08 5:40 ` Christoph Hellwig
2016-06-09 2:22 ` Dave Chinner
2016-06-09 2:53 ` Reinoud Koornstra
2016-06-09 2:56 ` Eric Sandeen
2016-06-09 3:42 ` Reinoud Koornstra
2016-06-15 5:40 ` Reinoud Koornstra
2016-06-22 1:42 ` Dave Chinner
2016-06-30 6:04 ` Daniel Wagner
2016-06-08 12:08 ` Daniel Wagner
2016-06-07 9:33 ` Reinoud Koornstra
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=20160607134442.GA1803@infradead.org \
--to=hch@infradead.org \
--cc=reinoudkoornstra@gmail.com \
--cc=sandeen@sandeen.net \
--cc=viro@zeniv.linux.org.uk \
--cc=wagi@monom.org \
--cc=xfs@oss.sgi.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