[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 Konstantin Belousov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Konstantin Belousov <[email protected]> --- (In reply to Mark Johnston from comment #0) For rwlock_destroy() this can be done, although I would be very careful with introducing such change. mutex_destroy() EINVAL caused too many grief. For cv_desstroy(), I do not see a good way to actually implement it. We have user/kernel sleeping threads, and although for user sleep this can be implemented with the same races as for mutex_destroy(), for kernel it seems to require new umtx op to cover just this case. I do not see it worth. -- 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]"