From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Olga Kornievskaia <kolga@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/5] Fix up delegation reclaim and recovery issues
Date: Wed, 12 Nov 2014 17:31:49 -0500 [thread overview]
Message-ID: <1415831514-47005-1-git-send-email-trond.myklebust@primarydata.com> (raw)
The main change w.r.t. the first iteration of these patches is that
we no longer trust the NFS_DELEGATED_STATE flag to tell us when we need
to test and/or discard the delegation. Instead, we just assume that
if we have a delegation then it is part of the recovery process.
Trond Myklebust (5):
NFSv4: Ensure that we remove NFSv4.0 delegations when state has
expired
NFSv4.1: nfs41_clear_delegation_stateid shouldn't trust
NFS_DELEGATED_STATE
NFSv4: Fix races between nfs_remove_bad_delegation() and delegation
return
NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are
revoked
NFS: Don't try to reclaim delegation open state if recovery failed
fs/nfs/delegation.c | 25 ++++++++++++--
fs/nfs/delegation.h | 1 +
fs/nfs/filelayout/filelayout.c | 3 --
fs/nfs/nfs4proc.c | 76 +++++++++++++++++++++++-------------------
4 files changed, 65 insertions(+), 40 deletions(-)
--
1.9.3
next reply other threads:[~2014-11-12 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 22:31 Trond Myklebust [this message]
2014-11-12 22:31 ` [PATCH v2 1/5] NFSv4: Ensure that we remove NFSv4.0 delegations when state has expired Trond Myklebust
2014-11-12 22:31 ` [PATCH v2 2/5] NFSv4.1: nfs41_clear_delegation_stateid shouldn't trust NFS_DELEGATED_STATE Trond Myklebust
2014-11-12 22:31 ` [PATCH v2 3/5] NFSv4: Fix races between nfs_remove_bad_delegation() and delegation return Trond Myklebust
2014-11-12 22:31 ` [PATCH v2 4/5] NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are revoked Trond Myklebust
2014-11-12 22:31 ` [PATCH v2 5/5] NFS: Don't try to reclaim delegation open state if recovery failed 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=1415831514-47005-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=kolga@netapp.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