linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chucklever@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFS server regression in v4.10-rc7
Date: Thu, 9 Feb 2017 05:21:36 -0800	[thread overview]
Message-ID: <20170209132136.GA23906@infradead.org> (raw)
In-Reply-To: <BF7B504A-A68C-45CB-8CA9-990F3AB2F1D6@gmail.com>

On Wed, Feb 08, 2017 at 04:54:02PM -0500, Chuck Lever wrote:
> I see this with my tmpfs export.

The tests passes fine for me with latests mainline on either tmpfs
or xfs.  This is on a 64-bit x86 VM.

  reply	other threads:[~2017-02-09 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24  8:22 [PATCH v2] nfsd: special case truncates some more Christoph Hellwig
2017-01-24 14:06 ` Jeff Layton
2017-01-24 22:03   ` J. Bruce Fields
2017-02-08 21:27 ` NFS server regression in v4.10-rc7 Chuck Lever
2017-02-08 21:39   ` Christoph Hellwig
2017-02-08 21:54     ` Chuck Lever
2017-02-09 13:21       ` Christoph Hellwig [this message]
2017-02-09 13:43         ` Christoph Hellwig

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=20170209132136.GA23906@infradead.org \
    --to=hch@infradead.org \
    --cc=chucklever@gmail.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).