Do not attempt to read JavaThread state from non-JavaThread threads#103
Merged
Conversation
Contributor
|
🔧 Report generated by pr-comment-scanbuild Scan-Build Report
Bug Summary
Reports
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contributor
richardstartin
approved these changes
May 31, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?:
The wallclock signal handler is trying to read Java thread state from the current thread indiscriminately and this means we might be accessing invalid memory for non-Java threads.
Unfortunately, the only way to test whether we are in a Java or attached Java thread (which can be resolved to jthread and therefore reading its state is valid) is to try and get the JNI environment. And that's what we do here.
Motivation:
This issue is flagged by ASAN but it can also lead to very weird thread states reported for non-Java threads.
Additional Notes:
Asan CI run showing that this change is fixing the asan report - https://github.com/DataDog/java-profiler/actions/runs/9317890928
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance.Unsure? Have a question? Request a review!