linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	bfields@redhat.com, linux-nfs@vger.kernel.org,
	Benjamin Coddington <bcodding@redhat.com>
Subject: Re: nfsd crash when running xfstests/089
Date: Fri, 23 Sep 2016 09:40:54 -0700	[thread overview]
Message-ID: <20160923164054.GA31447@infradead.org> (raw)
In-Reply-To: <1474561258.9454.8.camel@redhat.com>

On Thu, Sep 22, 2016 at 12:20:58PM -0400, Jeff Layton wrote:
> I had a go at reproducing this, but no luck. I'm running generic/089 on
> a KVM guest client and with the server running on a different KVM
> guest. I'm using vhost-scsi to emulate a disk (thanks to Ben Coddington
> for the help setting that up, btw...)

FYI, I've just used a single guest with both client and server in it
to reproduce as well.  In that case I'll have to use blocklayout, though
as the scsilayout requires separate systems for the reservations.

> In any case, I'll poke at it again if I get time. In the meantime, if
> you're able to get a vmcore, maybe take a look and see if you can
> figure out what's actually bad there? How far does it get in chasing
> the pointer to the cl_lock in release_lock_stateid?

How do I get a vmcore under kvm?

FYI, in the meantime I've also managed to reproduce it without pNFS,
althought it seems to take much longer to trigger.  One interesting
thing is that it seem to only happen when the host system has a heavy
CPU load (e.g. building a kernel).

Also I think I've always only reproduce it as part of a xfstests
./check -nfs -g auto, never by just running the test standalone.

  reply	other threads:[~2016-09-23 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 16:37 nfsd crash when running xfstests/089 Christoph Hellwig
2016-09-20 17:41 ` Jeff Layton
2016-09-22 16:20 ` Jeff Layton
2016-09-23 16:40   ` Christoph Hellwig [this message]
2016-09-23 17:42     ` Benjamin Coddington

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=20160923164054.GA31447@infradead.org \
    --to=hch@infradead.org \
    --cc=bcodding@redhat.com \
    --cc=bfields@redhat.com \
    --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).