The FILE_LOCK() implementation uses pool mutex under the hood, which
means it should only be used as a leaf level mutex. The fdrop_locked()
code wants to be called with FILE_LOCK() held, but the fdrop_locked()
implementation calls mtx_lock(Giant) before calling FILE_UNLOCK(). In
addition to
On Tue, 17 Jun 2003, Don Lewis wrote:
The FILE_LOCK() implementation uses pool mutex under the hood, which
means it should only be used as a leaf level mutex. The fdrop_locked()
code wants to be called with FILE_LOCK() held, but the fdrop_locked()
implementation calls mtx_lock(Giant)
On 17 Jun, Robert Watson wrote:
On Tue, 17 Jun 2003, Don Lewis wrote:
The FILE_LOCK() implementation uses pool mutex under the hood, which
means it should only be used as a leaf level mutex. The fdrop_locked()
code wants to be called with FILE_LOCK() held, but the fdrop_locked()