Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Oct 2005 13:36:25 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        current@freeBSD.org
Subject:   new lockmgr leak
Message-ID:  <20051001173625.GB96922@xor.obsecurity.org>

next in thread | raw e-mail | index | archive | help

--98e8jtXdkpgskNou
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This machine was running HEAD from a week or two ago.  It does not use
nullfs, which was a previous source of lockmgr leaks (now might be
fixed, although I've seen indications they're not completely fixed).
It only mounts ufs filesystems and nfs, and none of these are
unmounted at runtime..so the source of the leak must be elsewhere.
Unfortunately, the ddb backtrace appears to be corrupted:

panic(c07125c0,2,0,0,0) at panic+0x60
userret(c61acaf0,f0530d38,9f,424,3) at userret+0xf3
syscall(3b,69a003b,bfbf003b,0,66efe00) at syscall+0x3c6
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (1024), eip = 0x28149a97, esp = 0xbfbfbd6c, ebp = 0xbfbfc288 ---

syscall 1024?  No such animal.

0xc07125c0:     userret: Returning with %d locks held.

The thread with the leak was:

41187 c621ea3c 4203 41186 41184 0004002 [CPU 0] md5

This was running md5 over some package files..about all I can think
might have happened is something removed a package at the time it was
being checksummed, but this shouldn't of course cause any problems.

Unfortunately I can't even take a dump on this machine, since twe is
broken.  So this probably isn't a very useful bug report, but it's
here in case it happens again to someone else.

Kris

--98e8jtXdkpgskNou
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDPskYWry0BWjoQKURAs2HAJ9jNSgW/55OgjamWtWytgDEMMdVpgCeIPfg
Zw0ZcaDh0Jy9YSwH7VPMFzs=
=Q32e
-----END PGP SIGNATURE-----

--98e8jtXdkpgskNou--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051001173625.GB96922>