RDKCOM-5502: RDKBDEV-3350 Fix sometimes syseventd crash when system boot up#188
Open
owen-lu-sercomm wants to merge 1 commit intordkcentral:developfrom
Open
RDKCOM-5502: RDKBDEV-3350 Fix sometimes syseventd crash when system boot up#188owen-lu-sercomm wants to merge 1 commit intordkcentral:developfrom
owen-lu-sercomm wants to merge 1 commit intordkcentral:developfrom
Conversation
0389918 to
639a8b9
Compare
Reason for change: Sometimes syseventd will crash during reboot longrun, after check, the crash caused by no mutex lock was added when calling the function free_global_trigger_list. Test Procedure: 1. do reboot longrun 2. during boot up, check if syseventd crash and check if wan up Risks: Low Signed-off-by: Owen Lu <owen_lu@sercomm.com>
639a8b9 to
8f30eb0
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reason for change:
Sometimes syseventd will crash during reboot longrun, after check, the crash caused by no mutex lock was added when calling the function free_global_trigger_list.
Test Procedure:
Risks: Low
Signed-off-by: Owen Lu owen_lu@sercomm.com