From: Christoph Hellwig <hch@infradead.org>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
Daniel Wagner <wagi@monom.org>,
viro@zeniv.linux.org.uk, xfs@oss.sgi.com
Subject: Re: crash in xfs in current
Date: Tue, 7 Jun 2016 22:40:30 -0700 [thread overview]
Message-ID: <20160608054030.GA27069@infradead.org> (raw)
In-Reply-To: <CAAA5faEDdR_L6y9ShhUcermgvjtmzNCzwoYeENjx+8RUEMdwaA@mail.gmail.com>
On Tue, Jun 07, 2016 at 10:40:11PM -0600, Reinoud Koornstra wrote:
> >> Is this correct?
That's correct!
> >> If so, let me build and test.
> >> Building it already as we speak, but it would be nice if you could
> >> confirm I'm actually testing the right thing.
> >> Though, wouldn't it be good to repro and get a core file as well?
> >> Or would the test of this commit narrow down the possibilities as well?
> >> Thanks,
> >>
> >> Reinoud.
> >>
> >
> > Ouch, forgive me for not responding inline previously.
> > For what it's worth, i've compiled the kernel and are running it as we speak.
> > Will do testing and let you know.
>
> Ok, going back to commit 555b67e4e729ca544bb4028ab12e532c68b70ddb
> brings the kernel back to 4.6-rc1.
> With that kernel I crash all over the place, so that's something I cannot run.
Oh. What kinds of crashes?
> Is there a way to get the 4.7-rc1 or rc2 without the commits for XFS?
I can't think of a good way unfortunately.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-08 5:40 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
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 [this message]
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=20160608054030.GA27069@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.