bin/94892: rpc.lockd does not interoperate with Solaris 10 under
valgrind
Stephen Hurd
shurd at sasktel.net
Fri Mar 24 02:20:17 UTC 2006
>Number: 94892
>Category: bin
>Synopsis: rpc.lockd does not interoperate with Solaris 10 under valgrind
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 24 02:20:14 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Stephen Hurd
>Release: 6.0-STABLE Sun Nov 20 12:45:37 CST 2005
>Organization:
>Environment:
FreeBSD server.hurd.local 6.0-STABLE FreeBSD 6.0-STABLE #2: Sun Nov 20 12:45:37 CST 2005 admin at server.hurd.local:/usr/src/sys/i386/compile/SERVER i386
>Description:
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.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list