From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH, RFC] nfsd: fix nfsd4_cb_recall_done error handling
Date: Mon, 22 Sep 2014 13:06:42 -0700 [thread overview]
Message-ID: <20140922200642.GA24361@infradead.org> (raw)
In-Reply-To: <CAHQdGtSGh0vTgXw_eib3EWwGY71bSmDZDEU3Z9FW_bV_FSG7zQ@mail.gmail.com>
On Mon, Sep 22, 2014 at 04:03:37PM -0400, Trond Myklebust wrote:
> We're also missing a handler for NFS4ERR_DELAY, which is listed as a
> legal response to CB_RECALL in both RFC5661 and RFC3530bis. As far as
> I can tell from the above, knfsd will currently take that to be a sign
> it should mark the callback path as being down...
Yes. I've got a fix of that further down in my queue with the pnfs
patches, just wanted to set this bit out first.
I plan to handle NFS4ERR_DELAY in the generic callback layer instead of
burderning it onto the individual callback implementations.
next prev parent reply other threads:[~2014-09-22 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 18:29 [PATCH, RFC] nfsd: fix nfsd4_cb_recall_done error handling Christoph Hellwig
2014-09-22 20:03 ` Trond Myklebust
2014-09-22 20:06 ` Christoph Hellwig [this message]
2014-09-22 20:25 ` J. Bruce Fields
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=20140922200642.GA24361@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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