diff options
| author | Anoop C S <anoopcs@redhat.com> | 2016-01-19 14:35:18 +0530 |
|---|---|---|
| committer | Niels de Vos <ndevos@redhat.com> | 2018-01-22 09:54:02 +0000 |
| commit | ec3df9e65a3a2e1005cd4d50d06a8819fd3ab5f6 (patch) | |
| tree | 847ac98b10927e4e1081ba35260beb4b18996d47 /api/src/gfapi.aliases | |
| parent | 10d74166f17fa44c06bd1357e0a4b0b052265425 (diff) | |
libgfapi: Add new api for supporting mandatory-locks
The current API for byte-range locks [glfs_posix_lock()] doesn't
allow applications to specify whether it is advisory or mandatory
type locks. This particular change is to introduce an extended
byte-range lock API with an additional argument for including
the byte-range lock mode to be one among advisory(default) or
mandatory. Patch also includes a gfapi test case which make use
of this new api to acquire mandatory locks.
Ref: https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.8/Mandatory%20Locks.md
Change-Id: Ia09042c755d891895d96da857321abc4ce03e20c
Updates #393
Signed-off-by: Anoop C S <anoopcs@redhat.com>
Diffstat (limited to 'api/src/gfapi.aliases')
| -rw-r--r-- | api/src/gfapi.aliases | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/api/src/gfapi.aliases b/api/src/gfapi.aliases index 41a01f842fd..88d361dc329 100644 --- a/api/src/gfapi.aliases +++ b/api/src/gfapi.aliases @@ -169,3 +169,4 @@ _pub_glfs_upcall_register _glfs_upcall_register$GFAPI_3.13.0 _pub_glfs_upcall_unregister _glfs_upcall_unregister$GFAPI_3.13.0 _pub_glfs_setfsleaseid _glfs_setfsleaseid$GFAPI_4.0.0 +_pub_glfs_file_lock _glfs_file_lock$GFAPI_4.0.0 |