Date: Fri, 11 Jan 2019 15:53:38 +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-ApDgBGyYbO@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 --- Comment #2 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #1) Sorry, can you explain why a new umtx op is needed? Can't the ucond's c_has_waiters field be used to determine whether threads are blocked in the kernel? Certainly this is racy if the thread calling pthread_cond_destroy() does not hold the associated mutex, but I can't see the need for a new umtx= op. --=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-ApDgBGyYbO>