[release/9.0] linux/arm64: Verify TLS resolver code

[github-actions]

Backport of #108419 to release/9.0

/cc @kunalspathak

Customer Impact

• Customer reported
• Found internally

With this issue, a simple hello world application containing ThreadLocal will not work if it is compiled as a "single-file app" on linux/arm64

Regression

• Yes
• No

In #106052, we added logic to invoke a routine that returns the TLS resolver method's instruction stream which we verify if it is as expected and if not, turn off TLS optimization. However, for Single app case, the code that returns the TLS resolver method was itself returning incorrect result and when we dereferenced it, we hit segfault. The fix was to check if the TLS resolver method itself is accurate.

Testing

We verified this locally with the fix as well as double checking in gdb and it worked. Unfortunately, there is no linux-arm64 testing for single-file apps and @agocke is working on adding it.

Risk

Medium: This gets triggered very early during JITing any method that contains TLS code.

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[jeffschwMSFT]

lgtm. please get a code review. we will take for consideration in 9 GA

[kunalspathak]

@davidwrighton PTAL