From dm@home.dinoex.sub.de  Wed Nov 19 00:15:10 2003
Return-Path: <dm@home.dinoex.sub.de>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D8D4C16A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 19 Nov 2003 00:15:10 -0800 (PST)
Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [212.184.201.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 14D2043F3F
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 19 Nov 2003 00:15:09 -0800 (PST)
	(envelope-from dm@home.dinoex.sub.de)
Received: from home.dinoex.sub.de (home.dinoex.sub.de [217.6.200.196])
	by uucp.dinoex.sub.de (8.12.10/8.12.10) with ESMTP id hAJ8F4HJ032517
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 19 Nov 2003 09:15:04 +0100 (CET)
	(envelope-from dm@home.dinoex.sub.de)
Received: (from dm@localhost)
	by home.dinoex.sub.de (8.12.10/8.12.9/Submit) id hAJ8F6Dx019025;
	Wed, 19 Nov 2003 09:15:06 +0100 (CET)
	(envelope-from dm)
Message-Id: <200311190815.hAJ8F6Dx019025@home.dinoex.sub.de>
Date: Wed, 19 Nov 2003 09:15:06 +0100 (CET)
From: dirk.meyer@dinoex.sub.org
Reply-To: dirk.meyer@dinoex.sub.org
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: lock order reversal
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         59455
>Category:       kern
>Synopsis:       [lor] lock order reversal
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 19 00:20:19 PST 2003
>Closed-Date:    Mon May 03 10:39:34 PDT 2004
>Last-Modified:  Sun Feb 15 19:06:47 UTC 2009
>Originator:     Dirk Meyer
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
privat
>Environment:

FreeBSD current.dinoex.sub.de 5.1-CURRENT FreeBSD 5.1-CURRENT #4: Tue Nov 11 22:06:00 CET 2003     root@current.dinoex.sub.de:/usr/obj/usr/src/sys/NET5  i386

>Description:

Nov 19 05:51:18 current kernel: Sleeping on "stopevent" with the following non-sleepable locks held:
Nov 19 05:51:18 current kernel: exclusive sleep mutex sigacts r = 0 (0xc4e34aa8) locked @ /usr/src/sys/kern/kern_synch.c:293
Nov 19 05:51:18 current kernel: lock order reversal
Nov 19 05:51:18 current kernel: 1st 0xc4e34aa8 sigacts (sigacts) @ /usr/src/sys/kern/kern_synch.c:293
Nov 19 05:51:18 current kernel: 2nd 0xc49337fc process lock (process lock) @ /usr/src/sys/kern/kern_synch.c:309
Nov 19 05:51:18 current kernel: Stack backtrace:
Nov 19 05:51:18 current kernel: Sleeping on "stopevent" with the following non-sleepable locks held:
Nov 19 05:51:18 current kernel: exclusive sleep mutex sigacts r = 0 (0xc4e34aa8) locked @ /usr/src/sys/kern/subr_trap.c:260
Nov 19 05:51:18 current kernel: Sleeping on "stopevent" with the following non-sleepable locks held:
Nov 19 05:51:18 current kernel: exclusive sleep mutex sigacts r = 0 (0xc4e34aa8) locked @ /usr/src/sys/kern/subr_trap.c:260

>How-To-Repeat:

	a client was mounting nfs from thsi machine.
	I can't reproduce it.

>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jhb 
State-Changed-When: Mon May 3 10:38:51 PDT 2004 
State-Changed-Why:  
This should be fixed with Robert Waton's fix to the sigacts locking around 
stopevents in the signal code in revision 1.265 of sys/kern/kern_sig.c. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=59455 
>Unformatted:
