[Bug 234805] pthread_*_destroy doesn't handle locked objects consistently
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jan 10 04:18:10 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234805
Konstantin Belousov <kib at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kib at FreeBSD.org
--- Comment #1 from Konstantin Belousov <kib at FreeBSD.org> ---
(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.
More information about the freebsd-threads
mailing list