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@xxxxxxxxx> wrote: > > On Wed, Jun 8, 2016 at 8:56 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> 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@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
