From: Eryu Guan <guaneryu@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: upstream server crash
Date: Mon, 24 Oct 2016 11:15:19 +0800 [thread overview]
Message-ID: <20161024031519.GN2462@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20161023182115.GA14481@fieldses.org>
On Sun, Oct 23, 2016 at 02:21:15PM -0400, J. Bruce Fields wrote:
> I'm getting an intermittent crash in the nfs server as of
> 68778945e46f143ed7974b427a8065f69a4ce944 "SUNRPC: Separate buffer
> pointers for RPC Call and Reply messages".
>
> I haven't tried to understand that commit or why it would be a problem yet, I
> don't see an obvious connection--I can take a closer look Monday.
>
> Could even be that I just landed on this commit by chance, the problem is a
> little hard to reproduce so I don't completely trust my testing.
I've hit the same crash on 4.9-rc1 kernel, and it's reproduced for me
reliably by running xfstests generic/013 case, on a loopback mounted
NFSv4.1 (or NFSv4.2), XFS is the underlying exported fs. More details
please see
http://marc.info/?l=linux-nfs&m=147714320129362&w=2
Thanks,
Eryu
next prev parent reply other threads:[~2016-10-24 3:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 18:21 upstream server crash J. Bruce Fields
2016-10-23 20:04 ` Chuck Lever
2016-10-23 20:14 ` J. Bruce Fields
2016-10-24 3:15 ` Eryu Guan [this message]
2016-10-24 13:31 ` Jeff Layton
2016-10-24 13:51 ` Chuck Lever
2016-10-24 15:19 ` Jeff Layton
2016-10-24 15:24 ` Jeff Layton
2016-10-24 15:55 ` Chuck Lever
2016-10-24 18:08 ` J. Bruce Fields
2016-10-24 19:17 ` Jeff Layton
2016-10-24 20:40 ` J. Bruce Fields
2016-10-24 21:38 ` Chuck Lever
2016-10-25 0:57 ` Jeff Layton
2016-10-25 1:00 ` Chuck Lever
2016-10-25 1:46 ` Jeff Layton
2016-10-25 2:02 ` Chuck Lever
2016-10-28 1:20 ` Chuck Lever
2016-10-28 20:50 ` J. Bruce Fields
2016-10-28 21:45 ` Chuck Lever
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=20161024031519.GN2462@eguan.usersys.redhat.com \
--to=guaneryu@gmail.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.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).