From owner-freebsd-current Wed Mar 3 1: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 6C3E214BEA for ; Wed, 3 Mar 1999 01:07:38 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 18969 invoked from network); 3 Mar 1999 09:07:19 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 3 Mar 1999 09:07:19 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id EAA00298; Wed, 3 Mar 1999 04:07:14 -0500 (EST) Message-Id: <199903030907.EAA00298@y.dyson.net> Subject: Re: lockmgr panic with mmap() In-Reply-To: from Brian Feldman at "Mar 2, 99 06:29:31 pm" To: green@unixhelp.org (Brian Feldman) Date: Wed, 3 Mar 1999 04:07:14 -0500 (EST) Cc: alc@cs.rice.edu, current@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman said: > > > > The lock manager isn't bright enough to detect that the process > > already holds a read lock when it attempts to get the write lock. > > Thus, you get the "thrd_sleep" instead of a panic. > > > > In short, same bug, different symptoms. > > > Ahh, makes sense. > > Quick question: how in the heck did you learn this whole VM system? > Alan has had a history helping on the VM code for quite a while, and has contributed some really good ideas. Frankly, he appears to understand the code as well as anyone does. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message