Date: Fri, 24 Mar 2006 17:30:24 GMT From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/94892: rpc.lockd does not interoperate with Solaris 10 under valgrind Message-ID: <200603241730.k2OHUOAe003020@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/94892; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: Stephen Hurd <shurd@sasktel.net> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/94892: rpc.lockd does not interoperate with Solaris 10 under valgrind Date: Fri, 24 Mar 2006 12:29:30 -0500 On Fri, Mar 24, 2006 at 02:19:59AM +0000, Stephen Hurd wrote: > When running a multithreaded program under valgrind which makes > heavy use of file locking, valgrind will hang in the lockd state and > be unkillable. This does not seem to be related to bin/80389 as > reverting lock_proc.c to 1.17 does not work around the problem. > NO_INET6 was set true for the world/kernel build. This is occuring > on an SMP system. > >How-To-Repeat: > Run a debug build of Synchronet (http://www.synchro.net/) under > valgrind on an NFS exported filesystem from a Solaris 10 box. Unfortunately rpc.lockd is just broken in about N ways. It needs a lot of work, and someone to do it. The workaround for now is not to use it. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603241730.k2OHUOAe003020>