From owner-freebsd-current Mon Mar 16 21:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27508 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:41:55 -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 VAA27487 for ; Mon, 16 Mar 1998 21:41:51 -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 FAA08882; Tue, 17 Mar 1998 05:40:57 GMT Date: Tue, 17 Mar 1998 14:40:57 +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: > - freeing of resources. When the file is unlinked, the > lower vnode still has a reference from the upper vnode > which is left until the upper vnode is recycled. Currently > null_inactive calls VOP_INACTIVE on the lower vnode. > This is wrong (e.g. a process directly accessing the lower > vnode will see a truncated file, which is an unintended > side effect). > > Symptom: Removing a file that has been opend via nullfs > will not necessarily free the space on the file system > before the null vnode is recycled. So did you delete VOP_INACTIVE(lowervp) from null_inactive and move the vrele to null_inactive from null_reclaim to fix this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message