kib 47566a8355 ufs: do not leave non-reclaimed vnodes with zero i_mode around. ... After a recent change, vput() relocks even the exclusively locked vnode before inactivating it. Before that, UFS could safely instantiate a vnode for cleared inode, then the last vput() after ffs_vgetf() noted that ip->i_mode == 0 and recycled. Now, it is possible for other threads to note the half-constructed vnode, e.g. to insert it into hash, which makes other threads to use it despite mode is zero, before inactivation and reclaim. Handle the found cases in SU code, by explicitly doing reclaim. Assert that other places get fully constructed inode from ffs_vgetf(), which cannot be cleared before dependencies are resolved. Reported and tested by: pho Reviewed by: mckusick Sponsored by: The FreeBSD Foundation MFC after: 1 week		2019-12-27 16:43:34 +00:00
..
ffs	ufs: do not leave non-reclaimed vnodes with zero i_mode around.	2019-12-27 16:43:34 +00:00
ufs	vfs: flatten vop vectors	2019-12-16 00:06:22 +00:00