From: Andy Adamson <andros@thnk.citi.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: nfsv4@linux-nfs.org, willy@debian.org
Subject: [PATCH 7 of 10] RESEND lease interfaces for version 4 NFSD
Date: Tue, 21 Sep 2004 18:36:11 -0400 [thread overview]
Message-ID: <1095804047.21441d5b.7@citi.umich.edu> (raw)
VFS: use the inode i_writecount to test for handing out a F_RDLCK lease.
Signed-off-by: Andy Adamson <andros@citi.umich.edu>
---
linux-2.6.9-rc2-andros/fs/locks.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff -puN fs/locks.c~setlease-fixme fs/locks.c
--- linux-2.6.9-rc2/fs/locks.c~setlease-fixme 2004-09-21 18:00:30.770289384 -0400
+++ linux-2.6.9-rc2-andros/fs/locks.c 2004-09-21 18:00:30.774288776 -0400
@@ -1278,10 +1278,9 @@ int __setlease(struct file *filp, long a
if (!flp || !(*flp) || !(*flp)->fl_lmops || !(*flp)->fl_lmops->fl_break)
goto out;
- /*
- * FIXME: What about F_RDLCK and files open for writing?
- */
error = -EAGAIN;
+ if ((arg == F_RDLCK) && (atomic_read(&inode->i_writecount) > 0))
+ goto out;
if ((arg == F_WRLCK)
&& ((atomic_read(&dentry->d_count) > 1)
|| (atomic_read(&inode->i_count) > 1)))
_
reply other threads:[~2004-09-21 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1095804047.21441d5b.7@citi.umich.edu \
--to=andros@thnk.citi.umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=willy@debian.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;
as well as URLs for NNTP newsgroup(s).