From owner-freebsd-current Tue Jun 11 20:23: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id D00E637B401 for ; Tue, 11 Jun 2002 20:22:57 -0700 (PDT) Received: from FreeBSD.org ([63.193.112.125]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GXK00GKIPE9BQ@mta6.snfc21.pbi.net> for current@freebsd.org; Tue, 11 Jun 2002 20:22:57 -0700 (PDT) Date: Tue, 11 Jun 2002 20:23:05 -0700 From: Jeffrey Hsu Subject: Re: Crash after world/kernel upgrade In-reply-to: <"Message from Tor.Egge"@cvsup.no.freebsd.org> "of Tue, 11 Jun 2002 16:27:32 GMT." <20020611162732B.tegge@cvsup.no.freebsd.org> To: Tor.Egge@cvsup.no.freebsd.org Cc: killer@lothlorien.no, current@freebsd.org Message-id: <0GXK00GKLPE9BQ@mta6.snfc21.pbi.net> MIME-version: 1.0 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > typo in unlocking (causing recursive lock instead) Fixed. Thanks. > lack of inet6 support for inpcb locking, e.g. no > handling of locks in in6_pcbdetach. > attempts to destroy held lock in in_pcbdetach Gurg, IPv6 isn't locked up yet! These must be the result of inadvertent interactions with the shared IPv4 code. I'll see what can be done to either mitigate the effects for IPv6 or quickly lock up v6. Jeffrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message