Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[release/9.0-staging] Fix calling convention mismatch in GC callouts - #111105

#111105
Merged
jeffschwMSFT merged 3 commits into
release/9.0-stagingdotnet/runtime:release/9.0-stagingfrom
backport/pr-110685-to-release/9.0-stagingdotnet/runtime:backport/pr-110685-to-release/9.0-stagingCopy head branch name to clipboard
Jan 8, 2025
Merged

[release/9.0-staging] Fix calling convention mismatch in GC callouts#111105
jeffschwMSFT merged 3 commits into
release/9.0-stagingdotnet/runtime:release/9.0-stagingfrom
backport/pr-110685-to-release/9.0-stagingdotnet/runtime:backport/pr-110685-to-release/9.0-stagingCopy head branch name to clipboard

Conversation

@github-actions

@github-actions github-actions Bot commented Jan 6, 2025

Copy link
Copy Markdown
Contributor

Backport of #110685 to release/9.0-staging

/cc @AaronRobinsonMSFT @MichalStrehovsky

Customer Impact

  • Customer reported
  • Found internally

The GC will crash in .NET 9 when published with native AOT on win-x86. A GC callback was defined with an incorrect calling convention. This was reported by a customer - #110607.

Related servicing issue: #110815

Regression

  • Yes
  • No

Support for x86_32 was introduced in .NET 9.

Testing

Validated this with the help of Windows Store owners.

Risk

Low

Fixes #110607.

The native side expects fastcall.

Filed #110684 on the test hole. We would have caught it during x86 bringup if this had _any_ tests since this is a guaranteed stack corruption and crash.
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

@AaronRobinsonMSFT AaronRobinsonMSFT added the Servicing-consider Issue for next servicing release review label Jan 6, 2025
@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 9.0.x milestone Jan 6, 2025

@jeffschwMSFT jeffschwMSFT left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm. we will take for consideration in 9.0.x

@jeffschwMSFT jeffschwMSFT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 8, 2025
@jeffschwMSFT jeffschwMSFT modified the milestones: 9.0.x, 9.0.2 Jan 8, 2025
@jeffschwMSFT
jeffschwMSFT merged commit 7a95474 into release/9.0-staging Jan 8, 2025
@jkotas
jkotas deleted the backport/pr-110685-to-release/9.0-staging branch January 8, 2025 19:37
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-NativeAOT-coreclr Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.