On Sat, 10 Jan 2026 08:15:59 GMT, Serguei Spitsyn <[email protected]> wrote:

>> An asynchronous handshake operation (`ThreadSelfSuspensionHandshakeClosure`) 
>> can be installed when the target thread is not in a `MountUnmountDisabler` 
>> scope. But the target thread can enter such scope by the time the operation 
>> is self-processed by the target thread.
>> 
>> This is fixed by a small tweak in the function
>> `HandshakeOperation* HandshakeState::get_op_for_self(bool allow_suspend, 
>> bool check_async_exception)`.
>> The tweak is to skip a `HandshakeOperation` if 
>> `_handshakee->is_vthread_transition_disabler() == true`, so the same 
>> temporary suspension disabling mechanism would be used as for 
>> `_handshakee->is_disable_suspend() == true`.
>> 
>> All other changes are to move the `is_vthread_transition_disabler()` out of 
>> DEBUG to product.
>> 
>> Testing:
>>  - In progress: mach5 tiers 1-6
>
> Serguei Spitsyn has updated the pull request incrementally with one 
> additional commit since the last revision:
> 
>   review: add a test reproducing the bug

The functional fix seems fine.

Could you provide a brief summary in the test about its structure and exactly 
what scenario it is creating to be tested - thanks.

-------------

PR Review: https://git.openjdk.org/jdk/pull/28740#pullrequestreview-3658499404

Reply via email to