From: trondmy@kernel.org
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Add support for application leases to NFSv4
Date: Thu, 20 May 2021 12:38:58 -0400 [thread overview]
Message-ID: <20210520163902.215745-1-trondmy@kernel.org> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
If the client holds a delegation, it should be able to offer all the
guarantees that are needed to support application leases and
delegations. The main use case here is when re-exporting NFSv4.
Trond Myklebust (4):
NFSv4: Fix delegation return in cases where we have to retry
NFSv4: Add lease breakpoints in case of a delegation recall or return
NFSv4: Add support for application leases underpinned by a delegation
NFS: nfs_find_open_context() may only select open files
fs/nfs/delegation.c | 94 ++++++++++++++++++++++++++++++++----------
fs/nfs/delegation.h | 1 +
fs/nfs/inode.c | 4 ++
fs/nfs/nfs4_fs.h | 4 +-
fs/nfs/nfs4file.c | 8 +++-
fs/nfs/nfs4proc.c | 37 +++++++++++++++++
include/linux/nfs_fs.h | 1 +
7 files changed, 126 insertions(+), 23 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-20 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:38 trondmy [this message]
2021-05-20 16:38 ` [PATCH 1/4] NFSv4: Fix delegation return in cases where we have to retry trondmy
2021-05-20 16:39 ` [PATCH 2/4] NFSv4: Add lease breakpoints in case of a delegation recall or return trondmy
2021-05-20 16:39 ` [PATCH 3/4] NFSv4: Add support for application leases underpinned by a delegation trondmy
2021-05-20 16:39 ` [PATCH 4/4] NFS: nfs_find_open_context() may only select open files trondmy
2021-05-20 18:29 ` [PATCH 1/4] NFSv4: Fix delegation return in cases where we have to retry J. Bruce Fields
2021-05-20 19:08 ` Trond Myklebust
2021-05-20 20:47 ` bfields
2021-05-20 21:14 ` Trond Myklebust
2021-05-21 20:23 ` bfields
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=20210520163902.215745-1-trondmy@kernel.org \
--to=trondmy@kernel.org \
--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