[Bug 234805] pthread_*_destroy doesn't handle locked objects consistently
| Newsgroups | gmane.os.freebsd.devel.threading |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234805 --- Comment #3 from Konstantin Belousov <[email protected]> --- (In reply to Mark Johnston from comment #2) My thought when I answered was that you do want to lock umtx queue lock before looking into the queue. If you are fine with the race described, so be it. The difference between mtx/rw and cv there is that most often case of destroying locked mutex and rwlock is when the thread that owns the lock destroys it, which makes the check relatively sane. For cv, thread which does destroy cannot sleep obviously so the check is always racy. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-threads To unsubscribe, send any mail to "[email protected]"