From owner-freebsd-current  Sun Nov 17 12:13:31 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6448537B401
	for <current@FreeBSD.ORG>; Sun, 17 Nov 2002 12:13:30 -0800 (PST)
Received: from outel.org (outel.org [168.150.177.152])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EAC1343E77
	for <current@FreeBSD.ORG>; Sun, 17 Nov 2002 12:13:29 -0800 (PST)
	(envelope-from qumqats@outel.org)
Received: from localhost (winxp [192.168.1.20])
	by outel.org (8.12.6/8.12.6) with ESMTP id gAHKDEPl006160
	for <current@FreeBSD.ORG>; Sun, 17 Nov 2002 12:13:19 -0800 (PST)
	(envelope-from qumqats@outel.org)
Date: Sun, 17 Nov 2002 12:11:01 -0800
From: "Joel M. Baldwin" <qumqats@outel.org>
Cc: current@FreeBSD.ORG
Subject: Re: more info from panic from running dnet on SMP kernel ( lock
 order reversal, recursed on non-recursive lock )
Message-ID: <248350118.1037535061@[192.168.1.20]>
In-Reply-To: <Pine.NEB.3.96L.1021117145242.93303I-100000@fledge.watson.org>
References:  <Pine.NEB.3.96L.1021117145242.93303I-100000@fledge.watson.or
 g>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

--On Sunday, November 17, 2002 2:54 PM -0500 Robert Watson 
<rwatson@FreeBSD.ORG> 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
> robert@fledge.watson.org      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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message