From: Trond Myklebust <trond.myklebust@primarydata.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Fix NFS client state recovery
Date: Sat, 27 Sep 2014 18:20:13 -0400 [thread overview]
Message-ID: <1411856415-4472-1-git-send-email-trond.myklebust@primarydata.com> (raw)
- Fix up client to work with NFSv4/v4.1 all or nothing reboot recovery
- Fix open/state recovery error handling
Trond Myklebust (2):
NFSv4: Don't convert unreclaimed locks on STALE_CLIENTID
NFSv4: fix open/lock state recovery error handling
fs/nfs/nfs4state.c | 18 ++++++------------
1 file changed, 6 insertions(+), 12 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-27 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 22:20 Trond Myklebust [this message]
2014-09-27 22:20 ` [PATCH 1/2] NFSv4: Don't convert unreclaimed locks on STALE_CLIENTID Trond Myklebust
2014-09-27 22:20 ` [PATCH 2/2] NFSv4: fix open/lock state recovery error handling Trond Myklebust
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=1411856415-4472-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.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