From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 22 06:10:07 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9E4116A469 for ; Wed, 22 Aug 2007 06:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A0E0613C46A for ; Wed, 22 Aug 2007 06:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7M6A779052942 for ; Wed, 22 Aug 2007 06:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7M6A7Ze052941; Wed, 22 Aug 2007 06:10:07 GMT (envelope-from gnats) Date: Wed, 22 Aug 2007 06:10:07 GMT Message-Id: <200708220610.l7M6A7Ze052941@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-15?Q?Lars_K=F6ller?= Cc: Subject: Re: kern/115645: lockmgr: thread 0xc4c00d80, not exclusive lock holder 0xc4dd7c00 unlocking X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-15?Q?Lars_K=F6ller?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 06:10:07 -0000 The following reply was made to PR kern/115645; it has been noted by GNATS. From: =?ISO-8859-15?Q?Lars_K=F6ller?= To: bug-followup@FreeBSD.org, postmaster@uni-bielefeld.de Cc: lkoeller@freebsd.org Subject: Re: kern/115645: lockmgr: thread 0xc4c00d80, not exclusive lock holder 0xc4dd7c00 unlocking Date: Wed, 22 Aug 2007 08:09:07 +0200 Hi, why is kern/68757 still critical (submitted 2004), and our case only serious? I know release mgt of 7.0 costs a lot of time, but snapshot functionality hasn't reached production quality yet. I'm really amezed about that cause snapshots are introduced in 5.0. Perhaps it's a good idea to fix this problem before 7.0 release is out? Many thanks and regards Lars