the intent is retire LK_INTERLOCK support from vop_lock altogether to make it easier to have a non-lockmgr routine in there
```
commit 7a7d33a622a894549421eff0dd26b8830cc7a715
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Tue Sep 20 21:26:49 2022 +0000
vfs: stop passing LK_INTERLOCK to VOP_LOCK
Passing the lock down buys nothing, but instead requires locking
routines to be aware of its existence.
It gets dropped immediately if the vnode lock is already held,
meaning it does not protect the vnode from going away -- this is
typically handled by having the caller vhold the vnode first.
It does not prevent other threads from acquiring the vnode lock
either as there are plenty of places which do it without acquiring
the interlock first.
Note this does not remove the support yet.
commit c1e28f7f143e08b2d70ad0afba4030e249370941
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Tue Sep 20 20:53:41 2022 +0000
ufs: stop passing LK_INTERLOCK to vn_lock
The feature is going away.
```