linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jeff Layton <jlayton@poochiereds.net>,
	linux-nfs@vger.kernel.org, Kinglong Mee <kinglongmee@gmail.com>
Subject: Re: [RFC PATCH 2/2] nfsd: give up on CB_LAYOUTRECALLs after two lease periods
Date: Fri, 8 Jan 2016 14:36:31 -0500	[thread overview]
Message-ID: <20160108193631.GD5031@fieldses.org> (raw)
In-Reply-To: <20151222132538.GA25509@lst.de>

On Tue, Dec 22, 2015 at 02:25:38PM +0100, Christoph Hellwig wrote:
> Ok, this tests fine for me:
> 
> Tested-by: Christoph Hellwig <hch@lst.de>

Thanks, applying for 4.5.

(Missed your reviewed-by on the other patch when I submitted that for
stable, apologies.)

I did a little work on some pynfs tests to exercise some of the failure
cases here, but didn't get very far; I'll post something if I get a
chance to test them.  I think those tests are what we'd need before
doing something more sophisticated.

--b.

      reply	other threads:[~2016-01-08 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 12:23 [RFC PATCH 0/2] nfsd: clean up CB_LAYOUTRECALL handling Jeff Layton
2015-12-08 12:23 ` [RFC PATCH 1/2] nfsd: don't hold ls_mutex across a layout recall Jeff Layton
2015-12-08 15:19   ` Christoph Hellwig
2015-12-08 12:23 ` [RFC PATCH 2/2] nfsd: give up on CB_LAYOUTRECALLs after two lease periods Jeff Layton
2015-12-08 15:21   ` Christoph Hellwig
2015-12-08 15:46     ` Jeff Layton
2015-12-10 16:31       ` Christoph Hellwig
2015-12-22 13:25   ` Christoph Hellwig
2016-01-08 19:36     ` J. Bruce Fields [this message]

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=20160108193631.GD5031@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@lst.de \
    --cc=jlayton@poochiereds.net \
    --cc=kinglongmee@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).