Fix GetThreadStateTest #18660
Merged
Fix GetThreadStateTest #18660
Conversation
This file contains 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
|
jenkins test sanity.functional,sanity.openjdk,extended.openjdk alinux,aix jdk21 |
VirtualThreads.park performs operations in the below order: Set VThreadInspector to -1 and then acquire vmThreadListMutex JVMTI GetThreadState -> ... -> getVMThread follows the below order: Acquire vmThreadListMutex and then spin until VThreadInspector != -1 A deadlock occurs because the order of operations is inconsistent between VirtualThreads.park and JVMTI GetThreadState. To resolve the deadlock, the operations in getVMThread are swapped to match the operations in VirtualThreads.park: Acquire VThreadInspector and then acquire vmThreadListMutex Related: eclipse-openj9#18642 Signed-off-by: Babneet Singh <[email protected]>
RI and JTReg tests expect the same JVMTI thread state for - PARKED and PINNED - TIMED_PARKED and TIMED_PINNED Related: eclipse-openj9#18642 Signed-off-by: Babneet Singh <[email protected]>
|
jenkins test sanity.functional,sanity.openjdk,extended.openjdk alinux,aix jdk21 |
tajila
approved these changes
Dec 20, 2023
pshipton
approved these changes
Dec 20, 2023
This was referenced Dec 20, 2023
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.
Acquire VThreadInspector before vmThreadListMutex to avoid deadlock
VirtualThreads.parkperforms operations in the below order:Set
VThreadInspectorto-1and then acquirevmThreadListMutexJVMTI GetThreadState -> ... -> getVMThreadfollows the below order:Acquire
vmThreadListMutexand then spin untilVThreadInspector != -1A deadlock occurs because the order of operations is inconsistent
between
VirtualThreads.parkandJVMTI GetThreadState.To resolve the deadlock, the operations in
getVMThreadare swappedto match the operations in
VirtualThreads.park:Acquire
VThreadInspectorand then acquirevmThreadListMutexVirtualThread State: *PINNED is identical to *PARKED
RI and JTReg tests expect the same JVMTI thread state for
PARKEDandPINNEDTIMED_PARKEDandTIMED_PINNEDRelated: #18642
Signed-off-by: Babneet Singh [email protected]