[foreign-memaccess+abi] RFR: 8317514: Ensure MemorySegment is initialized before touching NativeMemorySegmentImpl [v2]

[Jorn Vernee]

On Mon, 9 Oct 2023 19:15:59 GMT, Jorn Vernee <jvernee at openjdk.org> wrote:

>> Please review this fix for a class initializer deadlock.
>> 
>> The issue is that `MemorySegment` references `NativeMemorySegmentImpl` in its initializer, through the `NULL` constant. `NativeMemorySegmentImpl` also depends on `MemorySegment` to be initialized, since it's a super interface with default methods. The VM does not drop the initialization monitor of `NativeMemorySegmentImpl` while trying to initialize super classes/interfaces (as mandated by the JVM spec).
>> 
>> When 2 threads try to intialize `MemorySegment` (e.g. through `ofAddress`) and `NativeMemorySegmentImpl` (e.g. through Arena::allocateFrom), at the same time, a deadlock can occur.
>> 
>> This PR fixes this issue by ensuring `MemorySegment` is initialized in all cases where we directly access `NativeMemorySegmentImpl` or `MappedMemorySegmentImpl`.
>> 
>> We might consider a fix that removes the cycle in the future as well.
>
> Jorn Vernee has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Add test for FileChannel::map

Superseded by: https://github.com/openjdk/jdk/pull/16187

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

PR Comment: https://git.openjdk.org/panama-foreign/pull/902#issuecomment-1762313431