--On Sunday, November 17, 2002 2:54 PM -0500 Robert Watson
<[EMAIL PROTECTED]> wrote:
Hmm. It looks like there is indeed a lock leak in the RFTHREAD code.
Maybe a change like the following might help:
PROC_LOCK(p2);
psignal(p2, SIGKILL);
PROC_UNLOCK(p2);
}
Change the } to:
} else
PROC_UNLOCK(p1->p_leader);
And see if that gets rid of the problem. Any chance this is highly
reproduceable, btw? :-) And what app are you running that's using
RFTHREAD -- linux thread stuff?
What source file would this be in?
Yes, it is 100% reproduceable
dnet is the distrubuted.net client for their various distributed
computing projects. <http://distributed.net/download/>
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Sun, 17 Nov 2002, Joel M. Baldwin wrote:
running dnet on a SMP kernel causes the kernel to panic.
lock order reversal
1st 0xc2c803e8 process lock (process lock) @
. . . snip . . .
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
