Konstantin Belousov 6470c8d3db Rework v_object lifecycle for vnodes. ... Current implementation of vnode_create_vobject() and vnode_destroy_vobject() is written so that it prepared to handle the vm object destruction for live vnode. Practically, no filesystems use this, except for some remnants that were present in UFS till today. One of the consequences of that model is that each filesystem must call vnode_destroy_vobject() in VOP_RECLAIM() or earlier, as result all of them get rid of the v_object in reclaim. Move the call to vnode_destroy_vobject() to vgonel() before VOP_RECLAIM(). This makes v_object stable: either the object is NULL, or it is valid vm object till the vnode reclamation. Remove code from vnode_create_vobject() to handle races with the parallel destruction. Reviewed by: markj Tested by: pho Sponsored by: The FreeBSD Foundation Differential revision: https://reviews.freebsd.org/D21412		2019-08-29 07:50:25 +00:00
..
smbfs_io.c	Replay r349334 by markj accidentally reverted by r349352	2019-06-25 06:14:00 +00:00
smbfs_node.c	Rework v_object lifecycle for vnodes.	2019-08-29 07:50:25 +00:00
smbfs_node.h
smbfs_smb.c
smbfs_subr.c
smbfs_subr.h
smbfs_vfsops.c	Allocate pager bufs from UMA instead of 80-ish mutex protected linked list.	2019-01-15 01:02:16 +00:00
smbfs_vnops.c	[smbfs] Allow semicolon in mounts that support long names	2019-01-20 05:52:16 +00:00
smbfs.h