```
commit 480ed6b1d254ef459f649a1a8422b81d8307ab5e
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Mon Apr 24 16:46:27 2023 +0000
ufs: drop LK_SLEEPFAIL from ffs_sync
It was added to handle identitity changes, but these no longer happen
since vnodes became actually freeable.
Even so, the change was bogus in that restarts could in principle keep
happening.
Note the issue is not fully fixed yet, but this gets rid of the only
consumer of the flag to VOP_LOCK.
commit ac68c238252dbc76e1875e4ed9ecdb13e8241a3e
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Tue Sep 20 22:11:02 2022 +0000
vfs: retire LK_INTERLOCK support from 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.
commit f4bd5f647b9dedd07e929d254d8838ad22456520
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Tue Sep 20 22:09:14 2022 +0000
vfs: remove LK_INTERLOCK support from vget_finish
Note it is kept for vget.
commit b4442f21867525e7262b20249d3be9bfbf56d16d
Author: Mateusz Guzik <mjg@FreeBSD.org>
Date: Tue Sep 20 21:26:49 2022 +0000
vfs: stop passing LK_INTERLOCK to VOP_LOCK
Note this does not remove the support yet.
commit c18cd53852eb5f4886e5d0d5efefcd15f9ffc0fa
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.
```