From owner-freebsd-bugs@FreeBSD.ORG  Thu Mar 30 11:10:15 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CFF3116A422
	for <freebsd-bugs@hub.freebsd.org>;
	Thu, 30 Mar 2006 11:10:15 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CCB1143D48
	for <freebsd-bugs@hub.freebsd.org>;
	Thu, 30 Mar 2006 11:10:14 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2UBAELU059270
	for <freebsd-bugs@freefall.freebsd.org>; Thu, 30 Mar 2006 11:10:14 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2UBAEF0059266;
	Thu, 30 Mar 2006 11:10:14 GMT (envelope-from gnats)
Resent-Date: Thu, 30 Mar 2006 11:10:14 GMT
Resent-Message-Id: <200603301110.k2UBAEF0059266@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-bugs@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
	Tomas Olsson <tol@stacken.kth.se>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BFA5F16A423
	for <freebsd-gnats-submit@FreeBSD.org>;
	Thu, 30 Mar 2006 11:06:32 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8F60643D46
	for <freebsd-gnats-submit@FreeBSD.org>;
	Thu, 30 Mar 2006 11:06:32 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k2UB6VGC019684
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 30 Mar 2006 11:06:31 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k2UB6VTC019683;
	Thu, 30 Mar 2006 11:06:31 GMT (envelope-from nobody)
Message-Id: <200603301106.k2UB6VTC019683@www.freebsd.org>
Date: Thu, 30 Mar 2006 11:06:31 GMT
From: Tomas Olsson <tol@stacken.kth.se>
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-2.3
Cc: 
Subject: misc/95103: panic after mtx_destroy() on locked spinlock
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2006 11:10:15 -0000


>Number:         95103
>Category:       misc
>Synopsis:       panic after mtx_destroy() on locked spinlock
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 30 11:10:14 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Tomas Olsson
>Release:        5.5-BETA4
>Organization:
Stacken Computer Club
>Environment:
FreeBSD lab04.lab.it.su.se 5.5-BETA4 FreeBSD 5.5-BETA4 #0: Mon Mar 13 23:12:57 UTC 2006     root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
MUTEX(9) man page, under mtx_destroy() says:
    It is permissible to have a single hold count on a mutex when it is destroyed.

This does not seem to be the case when the mutex is a MTX_SPIN lock. I get a panic very soon after I call mtx_destroy() during kld unload unless the lock is released. Page fault in user mode seems to be a common panic "cause" for this.

With a MTX_DEF it appears to work according to docs.
>How-To-Repeat:
{
struct mtx lock;
mtx_init(&lock, "foo", NULL, MTX_SPIN);
mtx_lock_spin(&lock);
mtx_destroy(&lock);
}
(tried during kld unload)
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: