From: "J. Bruce Fields" <bfields@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
"J. Bruce Fields" <bfields@redhat.com>
Subject: [PATCH 2/7] locks: introduce new FL_DELEG lock flag
Date: Fri, 9 Mar 2012 17:29:29 -0500 [thread overview]
Message-ID: <1331332174-22621-2-git-send-email-bfields@redhat.com> (raw)
In-Reply-To: <20120309222114.GA22423@fieldses.org>
From: "J. Bruce Fields" <bfields@redhat.com>
For now FL_DELEG is just a synonym for FL_LEASE. So this patch doesn't
change behavior.
Next we'll modify break_lease to treat FL_DELEG leases differently, to
account for the fact that NFSv4 delegations should be broken in more
situations than Windows oplocks.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
---
fs/locks.c | 2 +-
fs/nfsd/nfs4state.c | 2 +-
include/linux/fs.h | 1 +
3 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index 637694b..ea07a98 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -131,7 +131,7 @@
#define IS_POSIX(fl) (fl->fl_flags & FL_POSIX)
#define IS_FLOCK(fl) (fl->fl_flags & FL_FLOCK)
-#define IS_LEASE(fl) (fl->fl_flags & FL_LEASE)
+#define IS_LEASE(fl) (fl->fl_flags & (FL_LEASE|FL_DELEG))
static bool lease_breaking(struct file_lock *fl)
{
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index 8670863..38562ee 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -2838,7 +2838,7 @@ static struct file_lock *nfs4_alloc_init_lease(struct nfs4_delegation *dp, int f
return NULL;
locks_init_lock(fl);
fl->fl_lmops = &nfsd_lease_mng_ops;
- fl->fl_flags = FL_LEASE;
+ fl->fl_flags = FL_DELEG;
fl->fl_type = flag == NFS4_OPEN_DELEGATE_READ? F_RDLCK: F_WRLCK;
fl->fl_end = OFFSET_MAX;
fl->fl_owner = (fl_owner_t)(dp->dl_file);
diff --git a/include/linux/fs.h b/include/linux/fs.h
index e537b67..9d7446e 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1085,6 +1085,7 @@ static inline int file_check_writeable(struct file *filp)
#define FL_POSIX 1
#define FL_FLOCK 2
+#define FL_DELEG 4 /* NFSv4 delegation */
#define FL_ACCESS 8 /* not trying to lock, just looking */
#define FL_EXISTS 16 /* when unlocking, test for existence */
#define FL_LEASE 32 /* lease held on this file */
--
1.7.5.4
next prev parent reply other threads:[~2012-03-09 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 22:38 [PATCH] vfs: take i_mutex on renamed file J. Bruce Fields
2012-03-05 22:43 ` J. Bruce Fields
[not found] ` <20120305224334.GB16444-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2012-03-09 22:21 ` J. Bruce Fields
2012-03-09 22:29 ` [PATCH 1/7] " J. Bruce Fields
2012-03-09 22:29 ` J. Bruce Fields [this message]
2012-03-09 22:29 ` [PATCH 3/7] locks: implement delegations J. Bruce Fields
[not found] ` <20120309222114.GA22423-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2012-03-09 22:29 ` [PATCH 4/7] locks: break delegations on unlink J. Bruce Fields
2012-03-09 22:29 ` [PATCH 5/7] locks: break delegations on rename J. Bruce Fields
2012-03-09 22:29 ` [PATCH 6/7] locks: break delegations on link J. Bruce Fields
2012-03-09 22:29 ` [PATCH 7/7] locks: break delegations on any attribute modification J. Bruce Fields
2012-03-20 19:27 ` [PATCH] vfs: take i_mutex on renamed file J. Bruce Fields
2012-04-10 13:07 ` 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=1331332174-22621-2-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).