Date: Thu, 10 Jan 2019 04:18:08 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 234805] pthread_*_destroy doesn't handle locked objects consistently Message-ID: <bug-234805-13406-PIpBha1bNX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234805-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-234805-13406@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234805 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #1 from Konstantin Belousov <kib@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 ha= ve 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234805-13406-PIpBha1bNX>