Regarding the issue of ucx khash assert

[EmmaLee-c]

First, call kh_get in the ucp_rkey_proto_resolve function. After judging that the key does not exist, call kh_put in the ucp_worker_add_rkey_config function to trigger ucs_assert_always (khret!=UCS_KH_PUT_KEY_PRESENT); Causing the application to exit abnormally.
May I ask why there is no lock here? Is serial sequential execution guaranteed in the design?

[yosefe]

Yes, the operations on the worker should be protected by global worker lock, according the the thread support level provided to ucp_worker_create()