From: Dave Chinner <david@fromorbit.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Daniel Wagner <wagi@monom.org>,
Eric Sandeen <sandeen@sandeen.net>,
viro@zeniv.linux.org.uk, xfs@oss.sgi.com
Subject: Re: crash in xfs in current
Date: Thu, 9 Jun 2016 12:22:38 +1000 [thread overview]
Message-ID: <20160609022238.GY26977@dastard> (raw)
In-Reply-To: <CAAA5faEDdR_L6y9ShhUcermgvjtmzNCzwoYeENjx+8RUEMdwaA@mail.gmail.com>
On Tue, Jun 07, 2016 at 10:40:11PM -0600, Reinoud Koornstra wrote:
> On Tue, Jun 7, 2016 at 10:16 PM, Reinoud Koornstra
> <reinoudkoornstra@gmail.com> wrote:
> > On Tue, Jun 7, 2016 at 5:40 PM, Reinoud Koornstra
> > <reinoudkoornstra@gmail.com> wrote:
> >> Hi Christoph,
> >>
> >> Now my git log show this:
> >>
> >> commit 555b67e4e729ca544bb4028ab12e532c68b70ddb
> >> Merge: 544ad71 ad438c4
> >> Author: Dave Chinner <david@fromorbit.com>
> >> Date: Fri May 20 10:34:00 2016 +1000
> >>
> >> Merge branch 'xfs-4.7-inode-reclaim' into for-next
> >>
> >> commit 544ad71fc8e20fb3a6f50f00d487751492cd8409
> >> Merge: 2a4ad58 e6b3bb7
> >> Author: Dave Chinner <david@fromorbit.com>
> >> Date: Fri May 20 10:33:38 2016 +1000
> >>
> >> Merge branch 'xfs-4.7-error-cfg' into for-next
> >>
> >> commit 2a4ad5894c819978dca5595396d54d51c3aca694
> >> Merge: a7792aa 6e3e6d5
> >> Author: Dave Chinner <david@fromorbit.com>
> >> Date: Fri May 20 10:33:17 2016 +1000
> >>
> >> Merge branch 'xfs-4.7-misc-fixes' into for-next
> >>
> >> commit a7792aad644a259375002db8c9d9e03fd50bf509
> >> Merge: 5b911354 3ab3ffc
> >> Author: Dave Chinner <david@fromorbit.com>
> >> Date: Fri May 20 10:32:35 2016 +1000
> >>
> >> Is this 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.
> Is there a way to get the 4.7-rc1 or rc2 without the commits for XFS?
In your Linus git tree:
$ git remote add xfsdev git://git.kernel.org/git/dgc/linux-xfs.git
$ git remote update
$ git checkout -b xfsdev-merge v4.6
$ git merge xfsdev/xfs-for-linus-4.7-rc1
And that should give you the XFS changes for 4.7-rc1 in a vanilla 4.6
tree. This merge is one of the things I test (i.e. send to my test
machiens for a round of xfstests and other stress) before sending a
pull request to Linus, so it should work just fine.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-09 2:23 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
2016-06-09 2:22 ` Dave Chinner [this message]
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=20160609022238.GY26977@dastard \
--to=david@fromorbit.com \
--cc=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.