From owner-freebsd-hackers Mon Feb 15 12:33:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01578 for freebsd-hackers-outgoing; Mon, 15 Feb 1999 12:33:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01570 for ; Mon, 15 Feb 1999 12:33:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA19277; Mon, 15 Feb 1999 12:33:19 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Feb 1999 12:33:19 -0800 (PST) From: Matthew Dillon Message-Id: <199902152033.MAA19277@apollo.backplane.com> To: "John S. Dyson" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: inode / exec_map interlock ? (Ask the authors) References: <199902152027.PAA01706@y.dyson.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :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 believe this to be a long standing bug, not something new. It just happens to be rather hard to reproduce, is all. :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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message