From: Andy Adamson <andros@thnk.citi.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: nfsv4@linux-nfs.org, willy@debian.org
Subject: [PATCH 10 of 10] RESEND lease interfaces for version 4 NFSD
Date: Tue, 21 Sep 2004 18:36:26 -0400 [thread overview]
Message-ID: <1095804047.21441d5b.10@citi.umich.edu> (raw)
VFS: add the new lock manager callbacks to the documentation
Signed-off-by: Andy Adamson <andros@citi.umich.edu>
---
linux-2.6.9-rc2-andros/Documentation/filesystems/Locking | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletion(-)
diff -puN Documentation/filesystems/Locking~lease-documentation Documentation/filesystems/Locking
--- linux-2.6.9-rc2/Documentation/filesystems/Locking~lease-documentation 2004-09-21 18:00:34.838670896 -0400
+++ linux-2.6.9-rc2-andros/Documentation/filesystems/Locking 2004-09-21 18:00:34.841670440 -0400
@@ -295,13 +295,19 @@ fl_release_private: yes yes
prototypes:
int (*fl_compare_owner)(struct file_lock *, struct file_lock *);
void (*fl_notify)(struct file_lock *); /* unblock callback */
+ void (*fl_copy_lock)(struct file_lock *, struct file_lock *);
+ void (*fl_release_private)(struct file_lock *);
+ void (*fl_break)(struct file_lock *); /* break_lease callback */
locking rules:
BKL may block
fl_compare_owner: yes no
fl_notify: yes no
+fl_copy_lock: yes no
+fl_release_private: yes yes
+fl_break: yes no
- Currently only NLM provides instances of this class. None of the
+ Currently only NFSD and NLM provide instances of this class. None of the
them block. If you have out-of-tree instances - please, show up. Locking
in that area will change.
--------------------------- buffer_head -----------------------------------
_
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.10@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).