[release/9.0] Fix memory corruption bug in virtual static method dispatch #107776
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
- Use `TypeHandle::CanCastTo` instead of `MethodTable::CanCastTo` - The issue is that the `MethodTable` api requires cooperative mode, and the `TypeHandle` supports either mode Fixes #107754
|
Tagging subscribers to this area: @mangod9 |
jkotas
approved these changes
Sep 13, 2024
jeffschwMSFT
approved these changes
Sep 13, 2024
2 tasks
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.
Backport of #107763 to release/9.0
/cc @davidwrighton
Customer Impact
This bug impacts customers who use the static virtual method feature in combination with interface variance. The only known repro today also requires default interface implementations. The failure mode for customers is memory corruption caused by access to the GC heap which is not synchronized with the GC. This was found when adjusting the runtime in .NET 10 to use a slightly different code path which exposed the bug in many more situations.
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
Newly written regression test, PR testing.
Risk
Low. The change calls a function which is already called in similar situations, and which is capable of doing the correct synchronization with the GC.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging, notrelease/X.0.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.