nimble/host: Rework locking in L2CAP #2144
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sjanc
force-pushed
the
l2cap_coc_lock
branch
3 times, most recently
from
0525578 to
e318c2d
Compare
Main goal here to cleanup how locking is being done in L2CAP code: - avoid double/nested locking - avoid lock-unlock-lock pattern due to public API calls from internal code - provide _nolock variants to be used internally - public API is locked wrapper around _nolock private API - avoid locking in FOO and unlocking in BAR function for code clarify
sjanc
force-pushed
the
l2cap_coc_lock
branch
from
e318c2d to
99caccb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Main goal here to cleanup how locking is being done in L2CAP code: