From owner-freebsd-fs Wed Aug 7 23: 1:35 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9B0A37B400 for ; Wed, 7 Aug 2002 23:01:33 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84EF843E4A for ; Wed, 7 Aug 2002 23:01:33 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 621A7AE03F; Wed, 7 Aug 2002 23:01:33 -0700 (PDT) Date: Wed, 7 Aug 2002 23:01:33 -0700 From: Alfred Perlstein To: "David E. Cross" Cc: fs@freebsd.org, guptar@cs.rpi.edu Subject: Re: vnodes (UFS journaling)? Message-ID: <20020808060133.GH10953@elvis.mu.org> References: <200208072140.g77Le5C78847@monica.cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200208072140.g77Le5C78847@monica.cs.rpi.edu> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * David E. Cross [020807 14:41] wrote: > Ok, we've noticed an "unfortunate" side-effect of our work. We leak data > (part of the journal shows up in other files). I think it is because > of our handling of the vnode, and it being reused for other files (as > oppsoed to trashing memory, etc. The entries it writes in the files are > valid). We've tried _not_ calling vput(jvp) on it after the initial > open but then any access to the file hangs the kernel (in inode). How > can we say "don't reuse this" but allow other people to access it? VOP_UNLOCK? :) -- -Alfred Perlstein [alfred@freebsd.org] [#bsdcode/efnet/irc.prison.net] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message