diff options
author | M. Mohan Kumar | 2010-09-27 12:22:13 +0530 |
---|---|---|
committer | Eric Van Hensbergen | 2010-10-28 09:08:47 -0500 |
commit | 1d769cd192fc8c4097b1e2cd41fdee6ba3d1b2af (patch) | |
tree | 16fd71ff9178bbfe144a28a2e168c85fb541a11b /README | |
parent | a099027c779068b834f335cfdc3f2bf10f531dd9 (diff) |
9p: Implement TGETLOCK
Synopsis
size[4] TGetlock tag[2] fid[4] getlock[n]
size[4] RGetlock tag[2] getlock[n]
Description
TGetlock is used to test for the existence of byte range posix locks on a file
identified by given fid. The reply contains getlock structure. If the lock could
be placed it returns F_UNLCK in type field of getlock structure. Otherwise it
returns the details of the conflicting locks in the getlock structure
getlock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK
start[8] - Starting offset for lock
length[8] - Number of bytes to check for the lock
If length is 0, check for lock in all bytes starting at the location
'start' through to the end of file
pid[4] - PID of the process that wants to take lock/owns the task
in case of reply
client[4] - Client id of the system that owns the process which
has the conflicting lock
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions