Date: Fri, 2 Feb 2007 20:14:39 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Konstantin Belousov <kib@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern subr_witness.c Message-ID: <20070203041439.GB779@funkthat.com> In-Reply-To: <200702020902.l1292Js7068643@repoman.freebsd.org> References: <200702020902.l1292Js7068643@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Konstantin Belousov wrote this message on Fri, Feb 02, 2007 at 09:02 +0000:
> kib 2007-02-02 09:02:19 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern subr_witness.c
> Log:
> Record kqueue -> struct mount mtx -> vnode interlock lock order to
> catch the places where reverse lock order is instantiated.
Umm... does the above mean that kqueue can be obtained before mount,
and vnode interlock's? If so, that is incorrect, and it needs to be
that the kqueue lock is last... The lock order the kqueue is knlist
lock -> kqueue lock... Where knlist lock is the lock that protects
the object (or knlist belonging to the object)...
Do we have a way to signify that you do not obtain another lock once
you have obtained the kqueue lock?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070203041439.GB779>