[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[OpenAFS-port-freebsd] Re: FreeBSD 5.2.1 Client Success!
<<On Sat, 2 Oct 2004 03:05:50 -0400 (EDT), "David E. Cross" <crossd@xxxxxxxxxx> said:
> It _used_ to be that AFS kept an artificially incremente VNODE count to
> prevent "its" vnodes from re-entering the system pool, there were more
> than a couple of places that this cause various OS assumptions to be
I changed this last year: an afsnode HAS-A vnode now instead of IS-A.
> panic: lockmgr: locking against myself
Anyone working on this code should compile the kernel with
DEBUG_VFS_LOCKS in order to get better assertions. Generally, the
problem is that some AFS vnops are called with the vnode locked, and
some not, and AFS doesn't keep track down the call graph of which case
the current operation is. Often AFS will call back into the OSI layer
to do some manipulation of the underlying vnode which requires the
node to be locked.