From owner-freebsd-current@FreeBSD.ORG  Tue Aug 15 16:01:21 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
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 9DBE116A4E5
	for <current@freebsd.org>; Tue, 15 Aug 2006 16:01:21 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E739943D77
	for <current@freebsd.org>; Tue, 15 Aug 2006 16:01:20 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 9610746CB2;
	Tue, 15 Aug 2006 12:01:20 -0400 (EDT)
Date: Tue, 15 Aug 2006 17:01:20 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Peter Holm <peter@holm.cc>
In-Reply-To: <20060815154836.GA10128@peter.osted.lan>
Message-ID: <20060815165955.J45647@fledge.watson.org>
References: <20060815154836.GA10128@peter.osted.lan>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: current@freebsd.org
Subject: Re: panic: mutex nfsd_mtx not owned at nfs_srvsock.c:148
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2006 16:01:21 -0000


On Tue, 15 Aug 2006, Peter Holm wrote:

> While stress testing GENERIC HEAD from Aug 12 12:55 UTC I got this
> panic:
>
> panic: mutex nfsd_mtx not owned at
> ../../../nfsserver/nfs_srvsock.c:148
> cpuid = 2
> KDB: enter: panic
> [thread pid 761 tid 100096 ]
> Stopped at      kdb_enter+0x2b: nop
> db> where
> Tracing pid 761 tid 100096 td 0xc4041a20
> kdb_enter(c091cda8) at kdb_enter+0x2b
> panic(c091c0b7,c09210c9,c093241d,94,0,...) at panic+0x14b
> _mtx_assert(c0a64ec0,1,c093241d,94,c07ec53c,...) at _mtx_assert+0x66
> nfs_rephead(0,c52a0600,48,e662e964,e662e968,...) at nfs_rephead+0x25
> nfsrv_symlink(c52a0600,c4071e00,c4041a20,e662ec40) at
> nfsrv_symlink+0x3b7
> nfssvc_nfsd(c4041a20) at nfssvc_nfsd+0x409
> nfssvc(c4041a20,e662ed04) at nfssvc+0x18c
> syscall(3b,3b,3b,1,0,...) at syscall+0x256
>
> More details @ http://people.freebsd.org/~pho/stress/log/cons204.html

Could you use gdb to generate frame debugging information for the frame above 
nfs_rephead() (nfsrv_symlink()) also, please?  I'm a bit puzzled as to how 
things got into this state, as under normal circumstances, nfsm_reply() is the 
source of the nfs_rephead() call, and the NFS mutex is acquired the line 
before the call to nfsm_reply().

Thanks,

Robert N M Watson
Computer Laboratory
University of Cambridge