Get rid of the weird FSMID update path in the vnode and namecache code.
authorMatthew Dillon <dillon@dragonflybsd.org>
Tue, 25 Apr 2006 22:11:32 +0000 (22:11 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Tue, 25 Apr 2006 22:11:32 +0000 (22:11 +0000)
commit6b00893826c5112176acde734eb282f2eb82d3f7
treea52c6b9cea84b7be73795d9103ea33f0dd2ff548
parent577109ea34a9e1c288fd28329b0d1fe80bd20ab9
Get rid of the weird FSMID update path in the vnode and namecache code.
Instead, mark the vnode as needing an FSMID update when the vnode is
disconnected from the namecache.

This fixes a bug where FSMID updates were being lost at unmount time.
sys/kern/vfs_cache.c
sys/kern/vfs_subr.c
sys/kern/vfs_vopops.c
sys/sys/namecache.h
sys/sys/vfsops.h
sys/sys/vnode.h
sys/vfs/nfs/nfs_socket.c
sys/vfs/ufs/ufs_inode.c
sys/vfs/ufs/ufs_vnops.c