[release/5.0-rc2] Properly handle byrefs in tailcall helper stubs #41875
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 #41815 to release/5.0-rc2
/cc @BruceForstall @jakobbotsch
Customer Impact
This fixes a GC hole that could cause a crash or data corruption. This could happen in a small window for tail call functions via the new tailcall-via-helper mechanism if byref arguments were passed.
The original issue is #41555
Testing
Our full complement of CI GCStress runs was performed; the originally failing test was not observed to be failing any more. Additionally, @BruceForstall manually examined GC info for the tailcall helper stubs for the previously failing test, and observed the change looked correct.
Risk
low