[release/6.0] Add explicit null-check for tailcalls to VSD #62769
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 #62719 to release/6.0
/cc @jakobbotsch
Customer Impact
Certain reflection invocations and exception handling patterns that should throw NullReferenceException may instead crash the runtime due to an interaction between tailcalls to interface methods with a null receiver, and how the runtime maps access violations to NRE. Hit by customer in #61486.
Testing
Regression test included.
Regression
The same case reproduces in .NET 5, however the issue may be more common in .NET 6 because the JIT tailcalls more often.
Risk
Low, this changes the JIT to null-check ahead of time in this particular case.