summaryrefslogtreecommitdiffstats
path: root/include/linux/fcntl.h
diff options
context:
space:
mode:
authorMarc Eshel <eshel@almaden.ibm.com>2007-01-18 17:52:58 -0500
committerJ. Bruce Fields <bfields@citi.umich.edu>2007-05-06 20:38:28 -0400
commit9b9d2ab4154a42ea4a119f7d3e4e0288bfe0bb79 (patch)
tree62af6b2eff0885c26aa2af4b01890cc02cf0b2f0 /include/linux/fcntl.h
parent150b393456e5a23513cace286a019e87151e47f0 (diff)
downloadop-kernel-dev-9b9d2ab4154a42ea4a119f7d3e4e0288bfe0bb79.zip
op-kernel-dev-9b9d2ab4154a42ea4a119f7d3e4e0288bfe0bb79.tar.gz
locks: add lock cancel command
Lock managers need to be able to cancel pending lock requests. In the case where the exported filesystem manages its own locks, it's not sufficient just to call posix_unblock_lock(); we need to let the filesystem know what's happening too. We do this by adding a new fcntl lock command: FL_CANCELLK. Some day this might also be made available to userspace applications that could benefit from an asynchronous locking api. Signed-off-by: Marc Eshel <eshel@almaden.ibm.com> Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Diffstat (limited to 'include/linux/fcntl.h')
-rw-r--r--include/linux/fcntl.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/include/linux/fcntl.h b/include/linux/fcntl.h
index 996f561..40b9326 100644
--- a/include/linux/fcntl.h
+++ b/include/linux/fcntl.h
@@ -3,6 +3,10 @@
#include <asm/fcntl.h>
+/* Cancel a blocking posix lock; internal use only until we expose an
+ * asynchronous lock api to userspace: */
+#define F_CANCELLK (F_LINUX_SPECIFIC_BASE+5)
+
#define F_SETLEASE (F_LINUX_SPECIFIC_BASE+0)
#define F_GETLEASE (F_LINUX_SPECIFIC_BASE+1)
OpenPOWER on IntegriCloud