vfs: remove a stale comment about unlock + unref relationship in vput

It does not hold since introduction of vnode state tracking, which
validates unlock only happens after the target vnode is sorted out
(fully constructed or aborted). See 829f0bcb5fe24bb5 ("vfs: add the
concept of vnode state transitions").

1 files changed, 0 insertions, 5 deletions

diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c
index f86bda2aa6f0..fe299ecc9c56 100644
--- a/sys/kern/vfs_subr.c
+++ b/sys/kern/vfs_subr.c
@@ -3567,11 +3567,6 @@ enum vput_op { VRELE, VPUT, VUNREF };
  * exclusive lock on the vnode, while it is legal to call here with only a
  * shared lock (or no locks). If locking the vnode in an expected manner fails,
  * inactive processing gets deferred to the syncer.
- *
- * XXX Some filesystems pass in an exclusively locked vnode and strongly depend
- * on the lock being held all the way until VOP_INACTIVE. This in particular
- * happens with UFS which adds half-constructed vnodes to the hash, where they
- * can be found by other code.
  */
 static void
 vput_final(struct vnode *vp, enum vput_op func)