Subject: Re: panic: lockmgr: release of unlocked lock
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 01/11/2005 09:51:49
--lrZ03NoBR/3+SXJZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 11, 2005 at 06:02:00PM +0100, Manuel Bouyer wrote:
> On Mon, Jan 10, 2005 at 01:35:51PM -0800, Bill Studenmund wrote:
> > Can you get a line number for the above?
>=20
> It's the 2.0 GENERIC:
> NetBSD folk.lip6.fr 2.0 NetBSD 2.0 (GENERIC) #0: Tue Nov 30 21:04:03 UTC =
2004  builds@build:/big/builds/ab/netbsd-2-0-RELEASE/alpha/200411300000Z-ob=
j/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/alpha/compile/GENERIC alpha
>=20
> I can rebuild the kernel with -g if it helps. Would the cross-gdb in src/=
tools
> work from i386 on an alpha kernel ?

No idea.

> > > Just before the panic there is:
> > > vnode: table is full - increase kern.maxvnodes or NVNODE
> > >=20
> > > I don't know if it's related or not.
> >=20
> > It might be. Please also put a diagnostic printf() near line 473 of=20
> > layerfs_lookup(), in the if (error) case just after layer_node_create()=
.=20
> > There may be an inconsistency in how we handle an error in case that=20
> > create fails.
>=20
> What kind of diagnostic do you have in mind ? I'm sorry, but I don't know
> this part of the code so I don't know what to check ...

cnp->cn_flags would be good. Plus the simple fact of the printf happening=
=20
would help too. :-)

Somehow or another a parent directory is getting returned in the wrong=20
lock state. I'm not sure why...

Take care,

Bill

--lrZ03NoBR/3+SXJZ
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFB5BI1Wz+3JHUci9cRAkj9AJ0ROlsdrWfNDBW7J35BwmAO/8ilhACeOsCc
mtUl8bHlC6fFUmQmj8lsos0=
=mOHW
-----END PGP SIGNATURE-----

--lrZ03NoBR/3+SXJZ--