From owner-freebsd-net Wed Apr 17 16:40:15 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 228EC37B417 for ; Wed, 17 Apr 2002 16:40:07 -0700 (PDT) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020417234006.PEWD12144.rwcrmhc53.attbi.com@InterJet.elischer.org>; Wed, 17 Apr 2002 23:40:06 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA99042; Wed, 17 Apr 2002 16:25:32 -0700 (PDT) Date: Wed, 17 Apr 2002 16:25:31 -0700 (PDT) From: Julian Elischer To: Maksim Yevmenkin Cc: Roman Kurakin , freebsd-net@FreeBSD.ORG Subject: Re: 5.Current Netgraph, Mutex In-Reply-To: <3CBDA43E.87D2E163@digisle.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Roman, Having finally found the original mail, I concur. it looks like you have 'leaked' mutexes. (and the witness code accesses all mutexes even after the driver has unloaded... (*boom*)) I have not looked at the locks yet but you may be able to take advantage of netgraph's inherrant locking and queueing to simplify your usage of mutexes in some cases. (But I have to look at it more..) On Wed, 17 Apr 2002, Maksim Yevmenkin wrote: > Roman Kurakin wrote: > > > #if __FreeBSD_version >= 500000 > > mtx_init (&d->queue.ifq_mtx, "cp_queue", MTX_DEF); > > mtx_init (&d->hi_queue.ifq_mtx, "cp_queue_hi", MTX_DEF); > > #endif > > my guess would be that you forgot to call mtx_destroy() for > queue and hi_queue mutexes. > > thanks, > max > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message