Date: Wed, 7 Aug 2002 23:01:33 -0700 From: Alfred Perlstein <bright@mu.org> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: fs@freebsd.org, guptar@cs.rpi.edu Subject: Re: vnodes (UFS journaling)? Message-ID: <20020808060133.GH10953@elvis.mu.org> In-Reply-To: <200208072140.g77Le5C78847@monica.cs.rpi.edu> References: <200208072140.g77Le5C78847@monica.cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* David E. Cross <crossd@cs.rpi.edu> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020808060133.GH10953>