From: "William A.(Andy) Adamson" <andros@citi.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: andros@citi.umich.edu
Subject: PATCH [9/10] lease interfaces for version 4 NFSD
Date: Mon, 20 Sep 2004 16:23:10 -0400 [thread overview]
Message-ID: <20040920202310.828981BBA3@citi.umich.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 110 bytes --]
VFS: add the new lock manager callbacks to the documentation
Signed-off-by: Andy Adamson <andros@umich.edu>
[-- Attachment #2: linux-2.6.9-rc2-10-lease-doc.dif --]
[-- Type: text/plain , Size: 1107 bytes --]
diff --recursive -puN old/Documentation/filesystems/Locking new/Documentation/filesystems/Locking
--- old/Documentation/filesystems/Locking 2004-09-13 01:33:23.000000000 -0400
+++ new/Documentation/filesystems/Locking 2004-09-20 14:48:49.093136000 -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 -----------------------------------
next reply other threads:[~2004-09-20 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 20:23 William A.(Andy) Adamson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-20 20:23 PATCH [9/10] lease interfaces for version 4 NFSD William A.(Andy) Adamson
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=20040920202310.828981BBA3@citi.umich.edu \
--to=andros@citi.umich.edu \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).