xref: /freebsd/share/man/man9/lock.9 (revision 39beb93c3f8bdbf72a61fda42300b5ebed7390c8)
1.\"
2.\" Copyright (C) 2002 Chad David <davidc@acns.ab.ca>. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice(s), this list of conditions and the following disclaimer as
9.\"    the first lines of this file unmodified other than the possible
10.\"    addition of one or more copyright notices.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice(s), this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\"
15.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S) ``AS IS'' AND ANY
16.\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
17.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
18.\" DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY
19.\" DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
20.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
21.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
22.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
25.\" DAMAGE.
26.\"
27.\" $FreeBSD$
28.\"
29.Dd February 05, 2009
30.Dt LOCK 9
31.Os
32.Sh NAME
33.Nm lockinit ,
34.Nm lockdestroy ,
35.Nm lockmgr ,
36.Nm lockmgr_args ,
37.Nm lockmgr_args_rw ,
38.Nm lockmgr_disown ,
39.Nm lockmgr_printinfo ,
40.Nm lockmgr_recursed ,
41.Nm lockmgr_rw ,
42.Nm lockmgr_waiters ,
43.Nm lockstatus ,
44.Nm lockmgr_assert
45.Nd "lockmgr family of functions"
46.Sh SYNOPSIS
47.In sys/types.h
48.In sys/lock.h
49.In sys/lockmgr.h
50.Ft void
51.Fn lockinit "struct lock *lkp" "int prio" "const char *wmesg" "int timo" "int flags"
52.Ft void
53.Fn lockdestroy "struct lock *lkp"
54.Ft int
55.Fn lockmgr "struct lock *lkp" "u_int flags" "struct mtx *ilk"
56.Ft int
57.Fn lockmgr_args "struct lock *lkp" "u_int flags" "struct mtx *ilk" "const char *wmesg" "int prio" "int timo"
58.Ft int
59.Fn lockmgr_args_rw "struct lock *lkp" "u_int flags" "struct rwlock *ilk" "const char *wmesg" "int prio" "int timo"
60.Ft void
61.Fn lockmgr_disown "struct lock *lkp"
62.Ft void
63.Fn lockmgr_printinfo "struct lock *lkp"
64.Ft int
65.Fn lockmgr_recursed "struct lock *lkp"
66.Ft int
67.Fn lockmgr_rw "struct lock *lkp" "u_int flags" "struct rwlock *ilk"
68.Ft int
69.Fn lockmgr_waiters "struct lock *lkp"
70.Ft int
71.Fn lockstatus "struct lock *lkp"
72.Pp
73.Cd "options INVARIANTS"
74.Cd "options INVARIANT_SUPPORT"
75.Ft void
76.Fn lockmgr_assert "struct lock *lkp" "int what"
77.Sh DESCRIPTION
78The
79.Fn lockinit
80function is used to initialize a lock.
81It must be called before any operation can be performed on a lock.
82Its arguments are:
83.Bl -tag -width ".Fa wmesg"
84.It Fa lkp
85A pointer to the lock to initialize.
86.It Fa prio
87The priority passed to
88.Xr sleep 9 .
89.It Fa wmesg
90The lock message.
91This is used for both debugging output and
92.Xr sleep 9 .
93.It Fa timo
94The timeout value passed to
95.Xr sleep 9 .
96.It Fa flags
97The flags the lock is to be initialized with:
98.Bl -tag -width ".Dv LK_CANRECURSE"
99.It Dv LK_CANRECURSE
100Allow recursive exclusive locks.
101.It Dv LK_NOPROFILE
102Disable lock profiling for this lock.
103.It Dv LK_NOSHARE
104Allow exclusive locks only.
105.It Dv LK_NOWITNESS
106Instruct
107.Xr witness 4
108to ignore this lock.
109.It Dv LK_NODUP
110.Xr witness 4
111should log messages about duplicate locks being acquired.
112.It Dv LK_QUIET
113Disable
114.Xr ktr 4
115logging for this lock.
116.It Dv LK_TIMELOCK
117Use
118.Fa timo
119during a sleep; otherwise, 0 is used.
120.El
121.El
122.Pp
123The
124.Fn lockdestroy
125function is used to destroy a lock, and while it is called in a number of
126places in the kernel, it currently does nothing.
127.Pp
128The
129.Fn lockmgr
130and
131.Fn lockmgr_rw
132functions handle general locking functionality within the kernel, including
133support for shared and exclusive locks, and recursion.
134.Fn lockmgr
135and
136.Fn lockmgr_rw
137are also able to upgrade and downgrade locks.
138.Pp
139Their arguments are:
140.Bl -tag -width ".Fa flags"
141.It Fa lkp
142A pointer to the lock to manipulate.
143.It Fa flags
144Flags indicating what action is to be taken.
145.Bl -tag -width ".Dv LK_CANRECURSE"
146.It Dv LK_SHARED
147Acquire a shared lock.
148If an exclusive lock is currently held, it will be downgraded.
149.It Dv LK_EXCLUSIVE
150Acquire an exclusive lock.
151If an exclusive lock is already held, and
152.Dv LK_CANRECURSE
153is not set, the system will
154.Xr panic 9 .
155.It Dv LK_DOWNGRADE
156Downgrade exclusive lock to a shared lock.
157Downgrading a shared lock is not permitted.
158If an exclusive lock has been recursed, all references will be downgraded.
159.It Dv LK_UPGRADE
160Upgrade a shared lock to an exclusive lock.
161If this call fails, the shared lock is lost.
162During the upgrade, the shared lock could
163be temporarily dropped.
164Attempts to upgrade an exclusive lock will cause a
165.Xr panic 9 .
166.It Dv LK_RELEASE
167Release the lock.
168Releasing a lock that is not held can cause a
169.Xr panic 9 .
170.It Dv LK_DRAIN
171Wait for all activity on the lock to end, then mark it decommissioned.
172This is used before freeing a lock that is part of a piece of memory that is
173about to be freed.
174(As documented in
175.In sys/lockmgr.h . )
176.It Dv LK_SLEEPFAIL
177Fail if operation has slept.
178.It Dv LK_NOWAIT
179Do not allow the call to sleep.
180This can be used to test the lock.
181.It Dv LK_NOWITNESS
182Skip the
183.Xr witness 4
184checks for this instance.
185.It Dv LK_CANRECURSE
186Allow recursion on an exclusive lock.
187For every lock there must be a release.
188.It Dv LK_INTERLOCK
189Unlock the interlock (which should be locked already).
190.El
191.It Fa ilk
192An interlock mutex for controlling group access to the lock.
193If
194.Dv LK_INTERLOCK
195is specified,
196.Fn lockmgr
197and
198.Fn lockmgr_rw
199assume
200.Fa ilk
201is currently owned and not recursed, and will return it unlocked.
202See
203.Xr mtx_assert 9 .
204.El
205.Pp
206The
207.Fn lockmgr_args
208and
209.Fn lockmgr_args_rw
210function work like
211.Fn lockmgr
212and
213.Fn lockmgr_rw
214but accepting a
215.Fa wmesg ,
216.Fa timo
217and
218.Fa prio
219on a per-instance basis.
220The specified values will override the default
221ones, but this can still be used passing, respectively,
222.Dv LK_WMESG_DEFAULT ,
223.Dv LK_PRIO_DEFAULT
224and
225.Dv LK_TIMO_DEFAULT .
226.Pp
227The
228.Fn lockmgr_disown
229function switches the owner from the current thread to be
230.Dv LK_KERNPROC,
231if the lock is already held.
232.Pp
233The
234.Fn lockmgr_printinfo
235function prints debugging information about the lock.
236It is used primarily by
237.Xr VOP_PRINT 9
238functions.
239.Pp
240The
241.Fn lockmgr_recursed
242function returns true if the lock is recursed, 0
243otherwise.
244.Pp
245The
246.Fn lockmgr_waiters
247function returns true if the lock has waiters, 0 otherwise.
248.Pp
249The
250.Fn lockstatus
251function returns the status of the lock in relation to the current thread.
252.Pp
253When compiled with
254.Cd "options INVARIANTS"
255and
256.Cd "options INVARIANT_SUPPORT" ,
257the
258.Fn lockmgr_assert
259function tests
260.Fa lkp
261for the assertions specified in
262.Fa what ,
263and panics if they are not met.
264One of the following assertions must be specified:
265.Bl -tag -width ".Dv KA_UNLOCKED"
266.It Dv KA_LOCKED
267Assert that the current thread has either a shared or an exclusive lock on the
268.Vt lkp
269lock pointed to by the first argument.
270.It Dv KA_SLOCKED
271Assert that the current thread has a shared lock on the
272.Vt lkp
273lock pointed to by the first argument.
274.It Dv KA_XLOCKED
275Assert that the current thread has an exclusive lock on the
276.Vt lkp
277lock pointed to by the first argument.
278.It Dv KA_UNLOCKED
279Assert that the current thread has no lock on the
280.Vt lkp
281lock pointed to by the first argument.
282.El
283.Pp
284In addition, one of the following optional assertions can be used with
285either an
286.Dv KA_LOCKED ,
287.Dv KA_SLOCKED ,
288or
289.Dv KA_XLOCKED
290assertion:
291.Bl -tag -width ".Dv KA_NOTRECURSED"
292.It Dv KA_RECURSED
293Assert that the current thread has a recursed lock on
294.Fa lkp .
295.It Dv KA_NOTRECURSED
296Assert that the current thread does not have a recursed lock on
297.Fa lkp .
298.El
299.Pp
300.Sh RETURN VALUES
301The
302.Fn lockmgr
303and
304.Fn lockmgr_rw
305functions return 0 on success and non-zero on failure.
306.Pp
307The
308.Fn lockstatus
309function returns:
310.Bl -tag -width ".Dv LK_EXCLUSIVE"
311.It Dv LK_EXCLUSIVE
312An exclusive lock is held by the current thread.
313.It Dv LK_EXCLOTHER
314An exclusive lock is held by someone other than the current thread.
315.It Dv LK_SHARED
316A shared lock is held.
317.It Li 0
318The lock is not held by anyone.
319.El
320.Sh ERRORS
321.Fn lockmgr
322and
323.Fn lockmgr_rw
324fail if:
325.Bl -tag -width Er
326.It Bq Er EBUSY
327.Dv LK_FORCEUPGRADE
328was requested and another thread had already requested a lock upgrade.
329.It Bq Er EBUSY
330.Dv LK_NOWAIT
331was set, and a sleep would have been required.
332.It Bq Er ENOLCK
333.Dv LK_SLEEPFAIL
334was set and
335.Fn lockmgr
336or
337.Fn lockmgr_rw
338did sleep.
339.It Bq Er EINTR
340.Dv PCATCH
341was set in the lock priority, and a signal was delivered during a sleep.
342Note the
343.Er ERESTART
344error below.
345.It Bq Er ERESTART
346.Dv PCATCH
347was set in the lock priority, a signal was delivered during a sleep,
348and the system call is to be restarted.
349.It Bq Er EWOULDBLOCK
350a non-zero timeout was given, and the timeout expired.
351.El
352.Sh LOCKS
353If
354.Dv LK_INTERLOCK
355is passed in the
356.Fa flags
357argument to
358.Fn lockmgr
359or
360.Fn lockmgr_rw ,
361the
362.Fa ilk
363must be held prior to calling
364.Fn lockmgr
365or
366.Fn lockmgr_rw ,
367and will be returned unlocked.
368.Pp
369Upgrade attempts that fail result in the loss of the lock that
370is currently held.
371Also, it is invalid to upgrade an
372exclusive lock, and a
373.Xr panic 9
374will be the result of trying.
375.Sh SEE ALSO
376.Xr condvar 9 ,
377.Xr locking 9 ,
378.Xr mutex 9 ,
379.Xr rwlock 9 ,
380.Xr sleep 9 ,
381.Xr sx 9 ,
382.Xr mtx_assert 9 ,
383.Xr panic 9 ,
384.Xr VOP_PRINT 9
385.Sh AUTHORS
386This manual page was written by
387.An Chad David Aq davidc@acns.ab.ca .
388