From: <andros@netapp.com>
To: <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>, Andy Adamson <andros@netapp.com>
Subject: [PATCH Version 3 0/1] NFSv4.1: Fix an NFSv4.1 state renewal regression
Date: Mon, 29 Sep 2014 12:31:56 -0400 [thread overview]
Message-ID: <1412008317-36182-1-git-send-email-andros@netapp.com> (raw)
From: Andy Adamson <andros@netapp.com>
Version 3 responds to a review request by Trond:
The problem here isn't that we're failing to send a SEQUENCE in a
situation where we're not required to do so by the spec. The problem
is that we're failing to rearm renewd when we skip that SEQUENCE call.
Instead of removing them, could you rather please modify the above
lines to return an error, and then have nfs4_renew_state() respond by
calling nfs4_schedule_state_renewal(), instead of just skipping it as
we do today. In fact, AFAICS we want to do the same when the renew
call fails due to ENOMEM (but not when it returns EIO, since that
signals that the nfs_client is in the process of shutting down).
Andy Adamson (1):
NFSv4.1: Fix an NFSv4.1 state renewal regression
fs/nfs/nfs4proc.c | 2 +-
fs/nfs/nfs4renewd.c | 14 ++++++++++++--
2 files changed, 13 insertions(+), 3 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-09-29 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 16:31 andros [this message]
2014-09-29 16:31 ` [PATCH Version 3 1/1] NFSv4.1: Fix an NFSv4.1 state renewal regression andros
2014-09-29 17:10 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2014-09-29 16:29 [PATCH Version 3 0/1] " andros
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=1412008317-36182-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--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