linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Alexander Graf <agraf@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML List <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-nfs@vger.kernel.org, Jan Kara <jack@suse.cz>,
	skinsbursky@parallels.com, bfields@redhat.com
Subject: Re: [REGRESSION] nfsd crashing with 3.6.0-rc7 on PowerPC
Date: Fri, 28 Sep 2012 11:10:43 -0400	[thread overview]
Message-ID: <20120928151043.GA19102@fieldses.org> (raw)
In-Reply-To: <DC545CD9-8745-47DD-B13B-3385C0EB5B27@suse.de>

On Fri, Sep 28, 2012 at 04:19:55AM +0200, Alexander Graf wrote:
> 
> On 28.09.2012, at 04:04, Linus Torvalds wrote:
> 
> > On Thu, Sep 27, 2012 at 6:55 PM, Alexander Graf <agraf@suse.de> wrote:
> >> 
> >> Below are OOPS excerpts from different rc's I tried. All of them crashed - all the way up to current Linus' master branch. I haven't cross-checked, but I don't remember any such behavior from pre-3.6 releases.
> > 
> > Since you seem to be able to reproduce it easily (and apparently
> > reliably), any chance you could just bisect it?
> > 
> > Since I assume v3.5 is fine, and apparently -rc1 is already busted, a simple
> > 
> >   git bisect start
> >   git bisect good v3.5
> >   git bisect bad v3.6-rc1
> > 
> > will get you started on your adventure..
> 
> Heh, will give it a try :). The thing really does look quite bisectable.
> 
> 
> It might take a few hours though - the machine isn't exactly fast by today's standards and it's getting late here. But I'll keep you updated.

I doubt it's anything special about that workload, but just for kicks I
tried a "git clone -ls" (cloning my linux tree to another directory on
the same nfs filesystem), with server on 3.6.0-rc7, and didn't see
anything interesting (just an xfs lockdep warning that looks like this
one jlayton already reported:
http://oss.sgi.com/archives/xfs/2012-09/msg00088.html
)

Any (even partial) bisection results would certainly be useful, thanks.

--b.

  reply	other threads:[~2012-09-28 15:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  1:55 [REGRESSION] nfsd crashing with 3.6.0-rc7 on PowerPC Alexander Graf
2012-09-28  2:04 ` Linus Torvalds
2012-09-28  2:19   ` Alexander Graf
2012-09-28 15:10     ` J. Bruce Fields [this message]
2012-09-28 15:34       ` Alexander Graf
2012-10-01 14:03       ` Alexander Graf
2012-10-01 15:21         ` J. Bruce Fields
2012-10-02  0:58         ` Benjamin Herrenschmidt
2012-10-02 21:43           ` Nishanth Aravamudan
2012-10-02 21:47             ` Alexander Graf
2012-10-02 22:17               ` Nishanth Aravamudan
2012-10-02 22:31                 ` Alexander Graf
2012-10-04  0:26                   ` Anton Blanchard
2012-10-04  4:57                   ` [PATCH] powerpc/iommu: Fix multiple issues with IOMMU pools code Anton Blanchard
2012-10-04 10:54                     ` Alexander Graf

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=20120928151043.GA19102@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=bfields@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=skinsbursky@parallels.com \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).