The following reply was made to PR kern/36572; it has been noted by GNATS.

From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
To: pooka@cs.hut.fi
Cc: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/36572: panic on NFS unmount
Date: Thu, 28 Jun 2007 22:00:50 +0900 (JST)

 > 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
 > around.
 
 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.
 
 YAMAMOTO Takashi