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
This file contains 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
Unlock has been used in one call, GetNodeStateObj, from jni to application onAttribute and onEvent code path in android callback, but other jni->application calls in onAttribute and onEvent code path also need use Unlock, so we remove unblock in GetNodeStateObj, apply it in the top of onAttribute and onEvent.
Generally any JNI->Application in android callback need unlock pattern in case potential reentrancy hang.
@yunhanw-google could you add in the description why this change was done? The summary just states what the code does, however it does not explain why this is required nor does it explain the removal of the unlock in GetNodeStateObj
@yunhanw-google could you add in the description why this change was done? The summary just states what the code does, however it does not explain why this is required nor does it explain the removal of the unlock in GetNodeStateObj
…k for android IM (project-chip#32217)
* add missing unlock for onattribute and onevent callback for android IM
* Restyled by whitespace
---------
Co-authored-by: Restyled.io <[email protected]>
huangxuyong
pushed a commit
to huangxuyong/connectedhomeip
that referenced
this pull request
Mar 19, 2024
…k for android IM (project-chip#32217)
* add missing unlock for onattribute and onevent callback for android IM
* Restyled by whitespace
---------
Co-authored-by: Restyled.io <[email protected]>
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.
Unlock has been used in one call, GetNodeStateObj, from jni to application onAttribute and onEvent code path in android callback, but other jni->application calls in onAttribute and onEvent code path also need use Unlock, so we remove unblock in GetNodeStateObj, apply it in the top of onAttribute and onEvent.
Generally any JNI->Application in android callback need unlock pattern in case potential reentrancy hang.