From owner-freebsd-hackers Mon Feb 15 13:44:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11243 for freebsd-hackers-outgoing; Mon, 15 Feb 1999 13:44:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA11232 for ; Mon, 15 Feb 1999 13:44:23 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 602 invoked from network); 15 Feb 1999 21:44:14 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 15 Feb 1999 21:44:14 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id QAA01873; Mon, 15 Feb 1999 16:44:14 -0500 (EST) Message-Id: <199902152144.QAA01873@y.dyson.net> Subject: Re: inode / exec_map interlock ? (Ask the authors) In-Reply-To: <199902152033.MAA19277@apollo.backplane.com> from Matthew Dillon at "Feb 15, 99 12:33:19 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Mon, 15 Feb 1999 16:44:14 -0500 (EST) Cc: dyson@iquest.net, freebsd-hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > :> > :I don't know what you are trying to do in your code, but there is alot of > :history of problems in that area. I suspect that you might be making one of > :the mistakes that we used to do, and there is a resource deadlock problem in > :that area. > > ??? I'm not making any mistakes as far as I can tell. I haven't touched > the locking in the map code. > > John, please... you have to get out of the habit of assuming that > everything is my fault. Either that or read the email more carefully. > I didn't say that. I ask that you try to COMMUNICATE with people, and not assume that we (the developers of the VM code) don't know about VM code. You asked a question about code running with YOUR version of the existing VM code, and make the assumption that it is a bug in the existing codebase, and perhaps it is abuse of the existing codebase. There are some difficult to properly handle problems associated with certain portions of the code, and you are welcome to communicate with DG, me or others if you need help. Without a review process of YOUR version of our VM code, we cannot tell what is going on. If the code isn't reviewed, then it will need to be. > > I believe this to be a long standing bug, not something new. It just > happens to be rather hard to reproduce, is all. > Yep, it is an issue of the exec_map being a limited resource (if it is the problem that I remember.) DG is more of the exec_map person (with the image-activators.) It is easy to prove the deadlock. -- 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-hackers" in the body of the message