Subject: Re: kern/36572: panic on NFS unmount
To: None <firstname.lastname@example.org>
From: YAMAMOTO Takashi <email@example.com>
Date: 06/28/2007 22:00:50
> And it can happen only in unmount(MNT_FORCE), since otherwise sillyrename
> holds a reference. This might actually be fairly easy to duplicate by
> opening a file, removing it and doing unmount -f.
> Maybe we should record a dependency to sillyrenamed nodes in the
> parent and force flushing of those before flushing the parent node.
> I'd tend to not care except that otherwise we leave .nfs-files hanging
right. (and there is revoke(2) as well.)
another easy way to fix it would be to save the filehandle of the parent
rather than its vnode pointer.