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: Wed, 22 Jun 2016 11:42:53 +1000 [thread overview]
Message-ID: <20160622014253.GS12670@dastard> (raw)
In-Reply-To: <CAAA5faGTL4i3YS_oLxoeetpsEt+q59dmc2L7Kc-b5khzoV0GvA@mail.gmail.com>
On Tue, Jun 14, 2016 at 11:40:23PM -0600, Reinoud Koornstra wrote:
> On Wed, Jun 8, 2016 at 9:42 PM, Reinoud Koornstra
> <reinoudkoornstra@gmail.com> wrote:
> > On Wed, Jun 8, 2016 at 8:56 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
> >> On 6/8/16 9:53 PM, Reinoud Koornstra wrote:
> >>
> >>>> 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
> >>>
> >>> Tried to do this:
> >>>
> >>> reinoud@router-dev:~/Downloads/kernel_current$ git remote add xfsdev
> >>> git://git.kernel.org/git/dgc/linux-xfs.git
> >>
> >> I think that should be:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
> >
> > Ok That worked better indeed. :)
>
> I've tested the way you and Dave described.
> Indeed, I do not see the issues appearing in that xfsdev tree.
> So it works good there.
> For verification, I tried when I was upon this state (so this is a good state):
Ok, that's good to hear. Now for some more testing: Al Viro just
pushed some fixes to the parallel lookup code that may fix this
problem. Al asked this question:
| Can that be triggered on 4e82901 + cherry-pick of e7d6ef979?
| Same for 9f541801 + e7d6ef979?
Those commits are all in the current Linus tree - would you be
able to test them? (i.e. check out tree to 4e82901, then just
cherry pick the single commit (e7d6ef979) on top of that).
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-22 1:43 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
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 [this message]
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=20160622014253.GS12670@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox