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

[release/7.0] Fixing compressed singlefile scenario on osx-arm64 #80283

Merged
merged 5 commits into from
Jan 11, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 6, 2023

Backport of #79894 to release/7.0

/cc @VSadov

Customer Impact

When a user creates an app that uses both singlefile and compression and targets osx-arm64, the app cannot run.

Testing

Manual testing of the scenario. Also ran related tests, which this change fixes as well.

Risk

Low. This is a small change.
The root cause was not setting MEM_RESERVE_EXECUTABLE flag for the memory allocated to decompress R2R assemblies.

Since this is on osx-arm64 we need to play by the W^X rules. It is not possible to make writeable memory executable later on osx-arm64, if it does not have this flag when allocated.

@ghost
Copy link

ghost commented Jan 6, 2023

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

Issue Details

Backport of #79894 to release/7.0

/cc @VSadov

Customer Impact

Testing

Risk

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-Single-File

Milestone: -

@VSadov VSadov requested a review from janvorli January 6, 2023 02:05
@VSadov VSadov added the Servicing-consider Issue for next servicing release review label Jan 6, 2023
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. we will take for consideration in 7.0.x

@jeffschwMSFT jeffschwMSFT added this to the 7.0.x milestone Jan 6, 2023
@jeffschwMSFT jeffschwMSFT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 10, 2023
@jeffschwMSFT jeffschwMSFT modified the milestones: 7.0.x, 7.0.3 Jan 10, 2023
@carlossanlop
Copy link
Member

Approved by Tactics (7.0.3).
Signed off by area owners.
No OOB changes needed (native coreclr code).
CI failure unrelated: #80284
Almost ready to merge. Just waiting for the slow Mono crossaot leg to finish. If nothing concerning shows up, I'll merge.

@carlossanlop
Copy link
Member

The Mono crossaot leg seems to be stuck. I'll merge the PR.

@carlossanlop carlossanlop merged commit ed6eab9 into release/7.0 Jan 11, 2023
@carlossanlop carlossanlop deleted the backport/pr-79894-to-release/7.0 branch January 11, 2023 05:43
@ghost ghost locked as resolved and limited conversation to collaborators Feb 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Single-File Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants