Sysman API is not thread-safe when the handle is same

I just want to confirm that this is the expected API behavior: When Sysman API (e.g., zesMemoryGetState) is called with same handle concurrently, they are not thread-safe.

Because almost all Sysman API doc (e.g., zesMemoryGetState Doc) says "The application may call this function from simultaneous threads.", I get an impression that all these functions are thread-safe in all cases. But in fact when calling it from concurrent threads using same handle, I get SIGABT due to memory corruption. So I guess that this "The application may call this function from simultaneous threads." requires different handles as described in the introduction section of LevelZero spec.

Start with the zesMemoryGetState documentation and the Level Zero introduction's multithreading and concurrency section linked in the report. Reproduce the concurrent same-handle call that causes SIGABT, then compare the observed behavior with the documented threading guarantees. Done means the expected handle-concurrency behavior is confirmed and the API documentation or implementation issue is clearly identified.