aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Layton <jlayton@primarydata.com>2014-08-12 10:38:07 -0400
committerJeff Layton <jlayton@primarydata.com>2014-08-14 10:08:20 -0400
commit2ece173e4715031c031de9114491eee80a69cf68 (patch)
treeae7ecd55bbe5e69667b3771ed529f7e5867a3bea
parent2dfb928f7e5977a3faac943c134bbda5ae492629 (diff)
downloadlinux-2ece173e4715031c031de9114491eee80a69cf68.tar.gz
locks: update Locking documentation to clarify fl_release_private behavior
Acked-by: J. Bruce Fields <bfields@fieldses.org> Signed-off-by: Jeff Layton <jlayton@primarydata.com>
-rw-r--r--Documentation/filesystems/Locking6
1 files changed, 5 insertions, 1 deletions
diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
index b18dd177902..f1997e9da61 100644
--- a/Documentation/filesystems/Locking
+++ b/Documentation/filesystems/Locking
@@ -349,7 +349,11 @@ prototypes:
locking rules:
inode->i_lock may block
fl_copy_lock: yes no
-fl_release_private: maybe no
+fl_release_private: maybe maybe[1]
+
+[1]: ->fl_release_private for flock or POSIX locks is currently allowed
+to block. Leases however can still be freed while the i_lock is held and
+so fl_release_private called on a lease should not block.
----------------------- lock_manager_operations ---------------------------
prototypes: