.TH "posix_lock_file" 9 "posix_lock_file" "25 May 1998" "Kernel Hacker's Manual" LINUX
.SH NAME
posix_lock_file \- 
.SH SYNOPSIS
.B "int" posix_lock_file
.BI "(struct file *" filp ","
.BI "struct file_lock *" caller ","
.BI "unsigned int " wait ");"
.SH ARGUMENTS
.IP "filp" 12
 The file to apply the lock to
.IP "caller" 12
 The lock to be applied
.IP "wait" 12
 1 to retry automatically, 0 to return -EAGAIN
.SH "DESCRIPTION"
Add a POSIX style lock to a file.
We merge adjacent locks whenever possible. POSIX locks are sorted by owner
task, then by starting address
.SH "KAI PETZKE WRITES"
To make freeing a lock much faster, we keep a pointer to the lock before the
actual one. But the real gain of the new coding was, that \fBlock_it\fP and
\fBunlock_it\fP became one function.
.SH "TO ALL PURISTS"
 Yes, I use a few goto's. Just pass on to the next function.