-
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 potential data race in ESProductResolver #46330
Fix potential data race in ESProductResolver #46330
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46330/42161 |
A new Pull Request was created by @wddgit for master. It involves the following packages:
@Dr15Jones, @cmsbuild, @makortel, @smuzaffar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
cache_.store(getAfterPrefetchImpl()); | ||
cache = cache_.load(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cache_.store(getAfterPrefetchImpl()); | |
cache = cache_.load(); | |
cache = cache_ = getAfterPrefetchImpl(); |
this may allow the compiler to generate more optimized code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Thanks, that is better.
123b6a1
to
53d2f30
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46330/42171 |
enable threading |
Pull request #46330 was updated. @Dr15Jones, @cmsbuild, @makortel, @smuzaffar can you please check and sign again. |
please test |
please test there was bug in cms-bot which is fix now |
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
Comparison differences are related to #39803 |
+core |
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 now be reviewed by the release team before it's merged. @mandrenguyen, @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
1-7 % "increase" in maxmemory report is likely related to #46359 |
+1 |
PR description:
Fixes a potential data race in ESProductResolver. Noticed while reading code for a different development. No one has reported an issue related to this. Probably it is not an actual issue because writing the same pointer value to the same memory location concurrently is not an actual problem on the CPUs we currently use, although technically it is a data race and might someday be a problem on CPUs in use in the future (we think...). This condition should also occur extremely rarely.
I removed the memory order specifications in this change because that is what we usually currently do, but if anyone thinks it worth it I will put them back. I just thought it was a remnant from when we used to use those in the early concurrency days.
Also removed an old comment about a global mutex that was removed a long time ago.
PR validation:
Existing unit tests pass. There shouldn't be any change in behavior or output.