-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[syncd] Move logSet logGet under mutex to prevent race condition #1505
base: master
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@kcudnik Can you raise a PR to 202405 to address conflict? |
after this will pass |
@kcudnik Would you please elaborate on what issue you saw without the fix? We saw an issue which I'm not sure whether it's the same |
Saw the referenced ticket:) |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
arm fail becaue of syslog pipeline, not related to PR |
/azp run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@kcudnik : can you create PR for 202405 ? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
Fixes: sonic-net/sonic-buildimage#21180
Mutex is added to protect m_logLevelMap when doing logSet from multiple thread