X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=Documentation%2Ffilesystems%2FLocking;h=4af288e38f138f0864865b01096bdd38fc5ad76e;hb=f82b4b6780afabce9d9a91c84fae17ec3d63b9d7;hp=3d92049ae71dd5589f73cb24cfa02e3fd11c838b;hpb=1c7dd2ff430fa14b45c9def54468e3a25ab8342b;p=deliverable%2Flinux.git

diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
index 3d92049ae71d..4af288e38f13 100644
--- a/Documentation/filesystems/Locking
+++ b/Documentation/filesystems/Locking
@@ -472,8 +472,6 @@ locking rules:
 	All may block except for ->setlease.
 	No VFS locks held on entry except for ->setlease.
 
-->setlease has the file_list_lock held and must not sleep.
-
 ->llseek() locking has moved from llseek to the individual llseek
 implementations.  If your fs is not using generic_file_llseek, you
 need to acquire and release the appropriate locks in your ->llseek().
@@ -496,6 +494,10 @@ components. And there are other reasons why the current interface is a mess...
 ->read on directories probably must go away - we should just enforce -EISDIR
 in sys_read() and friends.
 
+->setlease operations should call generic_setlease() before or after setting
+the lease within the individual filesystem to record the result of the
+operation
+
 --------------------------- dquot_operations -------------------------------
 prototypes:
 	int (*write_dquot) (struct dquot *);