Subject: Re: amd/nfs/vgone interaction.
To: Christos Zoulas <firstname.lastname@example.org>
From: Bill Studenmund <email@example.com>
Date: 02/12/2003 10:11:17
On Tue, 11 Feb 2003, Christos Zoulas wrote:
> On Feb 12, 4:41am, firstname.lastname@example.org (Frank van der Linden) wrote:
> -- Subject: Re: amd/nfs/vgone interaction.
> So are you fixing it, or should I? The larger story is: should VOP_RECLAIM
> be accessing v_mount? if not, then the code that puts the vnode on the
> free list should clear it.
VOP_RECLAIM accessing v_mount on mounted file systems is fine. On umounted
Assuming all of the timer cleanup is internal (not waiting for callbacks
or such that we have to answer to keep others going too), then Frank's
suggestion of moving the cleanup to VOP_INACTIVATE is fine.
Other solutions are to:
1) when unmounting, vgone all the vnodes on the file system
2) when unmounting, flag all the vnodes on the mountpint as "NFS DEAD" -
set an internal flag. Everything from then on ignores the mount info, and
waits for the eventual RECLAIM.