Kirk McKusick b70428b2f0 Cannot release vnode underlying the nullfs vnode in null_inactive ... as it leaves the nullfs vnode allocated, but with no identity. The effect is that a null mount can slowly accumulate all the vnodes in the system, reclaiming them only when it is unmounted. Thus the null_inactive state instead accelerates the release of the null vnode by calling vrecycle which will in turn call the null_reclaim operator. The null_reclaim routine then does the freeing actions previosuly (incorrectly) done in null_inactive.		2002-03-18 05:39:04 +00:00
..
null_subr.c
null_vfsops.c
null_vnops.c	Cannot release vnode underlying the nullfs vnode in null_inactive	2002-03-18 05:39:04 +00:00
null.h