-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Fix two spinlocks #44517
Fix two spinlocks #44517
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44517/39640
|
enable threading |
A new Pull Request was created by @wddgit for master. It involves the following packages:
@Dr15Jones, @cmsbuild, @sunilUIET, @AdrianoDee, @smuzaffar, @miquork, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test with #44447 |
type bug |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3ea906/38353/summary.html Comparison SummarySummary:
|
+core |
My feeling is that #43522 somehow caused globalEndLumi transitions to be actually run concurrently. This (and #44447) could be worth of backporting nevertheless (or, doing the backports could be cheaper than trying to fully understand why this situation didn't happen before). The fixed code are wrong in any case. |
+1 |
+pdmv |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will be automatically merged. |
PR description:
Fix two spin locks that had bugs. One in LogErrorEventFilter and one in Path. Both could cause rare data races and crashes.
The one in LogErrorEventFilter was causing rare crashes in the IBs recently and that caused us to notice the problem. This is a minimal fix. We are going to discuss this more and possibly make further changes related to this in the future. See Issue #44413 for discussion.
The problem in Path has been there 4 years and no one has noticed or connected any problems to it. The problem in LogErrorEventFilter has been there 5 years and the problems were only recently noticed. I'm not sure if this is worth back porting or not. The problem should be occurring only very rarely...
In part the fix is a test. The problems are not reproducible so we are not 100% sure this fixes the problem. We plan to observe the IBs after this is merged and see if the recently noticed problems stop occurring.
PR validation:
Relies on existing tests.