From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-nfs@vger.kernel.org
Subject: Re: 3.12-rc2 nfsd oops in nfsd_cache_lookup
Date: Mon, 2 Dec 2013 09:25:47 -0800 [thread overview]
Message-ID: <20131202172547.GA5211@infradead.org> (raw)
In-Reply-To: <20131202122219.043174d6@tlielax.poochiereds.net>
On Mon, Dec 02, 2013 at 12:22:19PM -0500, Jeff Layton wrote:
> Looks like a similar oops to the one reported here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1025907
>
> Do you have a way to reproduce this reliably?
Seem to happen about 2/3s of the time when running xfstests on a v3
export for me. The other one third create a different lockup in the
same test that I'm looking at at the moment.
next prev parent reply other threads:[~2013-12-02 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 10:29 3.12-rc2 nfsd oops in nfsd_cache_lookup Christoph Hellwig
2013-12-02 17:22 ` Jeff Layton
2013-12-02 17:25 ` Christoph Hellwig [this message]
2013-12-03 3:33 ` Minlan Wang
2013-12-03 10:59 ` Jeff Layton
2013-12-04 0:55 ` Minlan Wang
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=20131202172547.GA5211@infradead.org \
--to=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.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).