Date: Thu, 28 Nov 2002 04:35:50 -0800 From: Alfred Perlstein <bright@mu.org> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: freebsd-fs@freebsd.org Subject: Re: openafs question Message-ID: <20021128123550.GM16066@elvis.mu.org> In-Reply-To: <200211281128.gASBS2g04424@monica.cs.rpi.edu> References: <200211281128.gASBS2g04424@monica.cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* David E. Cross <crossd@cs.rpi.edu> [021128 03:28] wrote: > I've been working on the FreeBSD-OpenAFS port, and I seem to be down to > one last bug; I know what it is, I am just having trouble getting the > solution to it. > > First a quick description of what the code is doing... It maintains its > own set of vnodes, outside of the system pool, which it populates with > data (these are NEVER gotten with getnewvnode(9)). The problem arises > when one of these is used, and then free'd. The system decides to insert > it into the global vnode cache and use it for things like UFS. This is > bad for 2 reasons: Have getnewvnode add a flag to the vnode noting that it's meant for the global list, otherwise store a "free()" callback in the vnode to be called? -- -Alfred Perlstein [alfred@freebsd.org] '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?20021128123550.GM16066>