You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there are some locking issues in L2CAP code related to public functions being called from L2CAP internals, this leads to nested locks on HS lock (or awkward critical section breaking pattern with unlock(); foo(); lock() sequence)
In general we should have internal functions that assume lock is taken, and public API should be wrappers with lock on top of that.
The text was updated successfully, but these errors were encountered:
there are some locking issues in L2CAP code related to public functions being called from L2CAP internals, this leads to nested locks on HS lock (or awkward critical section breaking pattern with unlock(); foo(); lock() sequence)
In general we should have internal functions that assume lock is taken, and public API should be wrappers with lock on top of that.
The text was updated successfully, but these errors were encountered: