From owner-freebsd-bugs  Sat Aug 23 09:13:15 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA25967
          for bugs-outgoing; Sat, 23 Aug 1997 09:13:15 -0700 (PDT)
Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA25939;
          Sat, 23 Aug 1997 09:13:08 -0700 (PDT)
Received: from idt.unit.no (tegge@ikke.idi.ntnu.no [129.241.111.65])
	by pat.idi.ntnu.no (8.8.6/8.8.6) with ESMTP id SAA05507;
	Sat, 23 Aug 1997 18:12:48 +0200 (MET DST)
Message-Id: <199708231612.SAA05507@pat.idi.ntnu.no>
To: joerg@FreeBSD.ORG
Cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/3180
In-Reply-To: Your message of "Sat, 23 Aug 1997 07:16:18 -0700 (PDT)"
References: <199708231416.HAA19806@freefall.freebsd.org>
X-Mailer: Mew version 1.70 on Emacs 19.34.1
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 23 Aug 1997 18:12:47 +0200
From: Tor Egge <Tor.Egge@idi.ntnu.no>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Synopsis: mlock() causes panic: lockmgr: upgrade exclusive lock
> 
> State-Changed-From-To: open-feedback
> State-Changed-By: joerg
> State-Changed-When: Sat Aug 23 16:15:49 MEST 1997
> State-Changed-Why: 
> 
> Many things happened with the lock manager lately, can you verify the
> problem still exists?

The current lock manager still disallows upgrade of exclusive lock, as it
should.

The bug was fixed in revision 1.78 of vm_map.c, and the this PR 
should be closed.