Skip to content
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 race condition caused by updating interface map with exact target #55308

Merged
merged 1 commit into from
Jul 8, 2021

Conversation

davidwrighton
Copy link
Member

  • Change interface map reading to reliably perform a volatile load (without barrier)
  • When performing scan for exact interface match/match trhough SpecialMarkerTypeForGenericCasting, be careful to only read the map once and use that value for all comparisons
  • All other uses of InterfaceMapIterator have been audited, and look to be safe

This may fix #54941

- Change interface map reading to reliably perform a volatile load (without barrier)
- When performing scan for exact interface match/match trhough SpecialMarkerTypeForGenericCasting, be careful to only read the map once and use that value for all comparisons
- All other uses of InterfaceMapIterator have been audited, and look to be safe
@davidwrighton
Copy link
Member Author

/azp run help

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@davidwrighton
Copy link
Member Author

@VincentBu I've manually triggered the jit stress runs that were failing that caused you to file #54941. Could you take a look and see if the failures have been fixed by my change? See https://dev.azure.com/dnceng/public/_build/results?buildId=1225928&view=results

Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for fixing!

@VincentBu
Copy link
Contributor

@VincentBu I've manually triggered the jit stress runs that were failing that caused you to file #54941. Could you take a look and see if the failures have been fixed by my change? See https://dev.azure.com/dnceng/public/_build/results?buildId=1225928&view=results

I check this run and didn't find the failures.

@davidwrighton davidwrighton merged commit 9270b34 into dotnet:main Jul 8, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 7, 2021
@davidwrighton davidwrighton deleted the fix_load_problem branch April 13, 2023 18:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tests failed with error message: violates the constraint of type parameter 'T'.
3 participants