Date: Fri, 08 Aug 2003 14:28:31 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Sam Leffler <sam@FreeBSD.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: RE: PERFORCE change 35749 for review Message-ID: <XFMail.20030808142831.jhb@FreeBSD.org> In-Reply-To: <200308072230.h77MUtBU024118@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07-Aug-2003 Sam Leffler wrote: > http://perforce.freebsd.org/chv.cgi?CH=35749 > > Change 35749 by sam@sam_ebb on 2003/08/07 15:29:55 > > o must unlock before destroying mutex > o must lock rt_gwroute before freeing when cleaning up on error It's ok to own a mutex when you destroy it. It's actually fairly desirable in fact since it is a rather foolproof way of making sure someone eles doesn't own it. Of course, they could still be blocked on it.. :-/ -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030808142831.jhb>