Subject: Re: lockmgr: release of unlocked lock!
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 01/07/2005 10:50:10
--IrhDeMKUP4DT/M7F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 07, 2005 at 11:19:58AM +0100, Manuel Bouyer wrote:
> Hi,
> tonight the box I use for the NetBSD mirror paniced with:
> Panic: lockmgr: release of unlocked lock!
> Begin traceback
>  =20
> lockmgr ( cf5d5f9c,6,d058d858,cf5d5f9c,10002)
> layer_unlock+0x6b
> layer_inactive+0x2d
> vput+0x72
> lookup+0x2af
> namei+0x138
> vn_open+0x60f
> sys_open+0xcb
> syscall_plain+0x17e

I really can't tell what was wrong. All the calls in lookup() that call=20
vput() are releasing a parent directory that should be locked.

Take care,

Bill

--IrhDeMKUP4DT/M7F
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFB3tniWz+3JHUci9cRAhldAJ93FL8FNgBUf+C7Hl5LS9GN9HawVQCgixY/
BxTv108xSzf3V+1+/Fz1Rgo=
=sSzu
-----END PGP SIGNATURE-----

--IrhDeMKUP4DT/M7F--