Alfred Perlstein 92e73f5711 I ran into an nfs client panic a couple of times in a row over the ... last few days. I tracked it down to the fact that nfs_reclaim() is setting vp->v_data to NULL _before_ calling vnode_destroy_object(). After silence from the mailing list I checked further and discovered that ufs_reclaim() is unique among FreeBSD filesystems for calling vnode_destroy_object() early, long before tossing v_data or much of anything else, for that matter. The rest, including NFS, appear to be identical, as if they were just clones of one original routine. The enclosed patch fixes all file systems in essentially the same way, by moving the call to vnode_destroy_object() to early in the routine (before the call to vfs_hash_remove(), if any). I have only tested NFS, but I've now run for over eighteen hours with the patch where I wouldn't get past four or five without it. Submitted by: Frank Mayhar Requested by: Mohan Srinivasan MFC After: 1 week		2006-01-17 17:29:03 +00:00
..
hpfs_alsubr.c
hpfs_ioctl.h
hpfs_lookup.c
hpfs_subr.c
hpfs_subr.h
hpfs_vfsops.c	Normalize a significant number of kernel malloc type names:	2005-10-31 15:41:29 +00:00
hpfs_vnops.c	I ran into an nfs client panic a couple of times in a row over the	2006-01-17 17:29:03 +00:00
hpfs.h	XXX: unnecessary pointer in inode.	2005-03-16 07:21:38 +00:00
hpfsmount.h