libzfs is generally MT-unsafe. If these two threads are using the same libzfs_handle_t, things are going to go badly for many reasons, not just due to concurrent manipulation of libzfs_ns_avl. What's the rationale for adding locking to only this one part of libzfs?
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/433#issuecomment-319229303 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T1ceee7d74c7fab5d-Mbedf89f88858386e922e36e6 Powered by Topicbox: https://topicbox.com
