[release/7.0] Fix reserving executable memory as per allocation type in ClrVirtualAllocWithinRange()

[github-actions]

Backport of #83819 to release/7.0

/cc @janvorli @k15tfu

Customer Impact

A customers sometimes get a System.OutOfMemoryException exception in .NET 7 app on macOS ARM64 in arbitrary places. The issue is caused by a bug in the ClrVirtualAllocWithinRange specific to macOS. It happens when the application uses up all the executable memory preallocated at app start time and the ExecutableAllocator tries to allocate more using the ClrVirtualAllocWithinRange. That function doesn't set the special MEM_RESERVE_EXECUTABLE flag that causes the PAL to mmap the memory range with the MAP_JIT flag that enables the special Apple M1 processor support for regions that can be switched between read-execute and read-write modes per thread.

Testing

CI testing, local targeted testing

Risk

Low, the change is very small and only influences the problematic case and doesn't change any other behavior.

[janvorli]

In the failed leg, only one test has failed and that was with a known issue:
#83901

[jeffschwMSFT]

approved. we will take for consideration in 7.0.x

[carlossanlop]

I'm retargeting this PR to the new release/7.0-staging branch, which is the one that we will use from now on for servicing fixes.

Repo maintainers will now be allowed to merge their own servicing PR as long as it meets the requirements:

• It is approved by Tactics (signaled by adding the Servicing-approved label).
• It's signed-off by an area owner.
• The CI is green, or the failures are investigated as unrelated.
• And if the PR touches an OOB package, the necessary OOB authoring changes are added.

The new process is described here: runtime/docs/project/library-servicing.md.

The infra team will be actively monitoring servicing PRs to ensure all requirements are met and to help with any issues.

Let me know if you have any questions.

[carlossanlop]

Reminder: April 10th is the last day to merge backport PRs to ensure they get included in the May Release. PR owners are now in charge of merging their own PRs.

[janvorli]

@jkotas can you please approve this?

[janvorli]

@carlossanlop I can see that an extra commit 6a533c1 was added to this PR by dotnet-maestro. It updates emsdk version. I don't know why that happened - could it be some bad merge when you have retargetted this PR? I can see that wasm / tvos tests are failing, so I wonder if it is because of that.

[carlossanlop]

@carlossanlop I can see that an extra commit 6a533c1 was added to this PR by dotnet-maestro.

Not sure why that commit was added, but it shouldn't be there. Can you please remove it, @janvorli? The dependency flows are happening in separate automated PRs.

Edit: Fixed it with GitHub suggestions.

[AaronRobinsonMSFT]

@carlossanlop Any chance we can merge this isn now that it is green?