From owner-freebsd-current Fri Mar 13 21:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15001 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:38:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14985 for ; Fri, 13 Mar 1998 21:38:00 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA21918; Sat, 14 Mar 1998 05:37:10 GMT Date: Sat, 14 Mar 1998 14:37:10 +0900 (JST) From: Michael Hancock To: Tor Egge cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <199803131845.TAA26656@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Mar 1998, Tor Egge wrote: > I've been using nullfs since Nov 7 1997 without any serious problems > after having fixed some of the above mentioned problems in my local > source tree. The code is not perfect, panics are still possible due > to heuristics (due to VOP_ISLOCKED()) being wrong, but I've yet > not experienced any problems. What would you need to do to fix VOP_ISLOCKED()? Does it really make sense to have an VOP_ISLOCKED()? This ownership issue looks like a big can of worms. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message