Date: Fri, 28 Aug 2015 07:30:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 200992] proccess won't die in thread_suspend_switch Message-ID: <bug-200992-16-I5zIkA3sbW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200992-16@https.bugs.freebsd.org/bugzilla/> References: <bug-200992-16@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=200992 --- Comment #13 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Hans Petter Selasky from comment #12) This is an layer that makes the locks work, there is no mutexes which you can lock safely. Even if the callout KPI is extended to support interlocking with spinlock, this would still not provide anything to the case, because the only natural spinlock there is thread lock, which is not real spinlock and useless for the interlocking pattern. The case there is inherently racy, similar to how locks implementations are racy due to the nature of the code, and must be correctly supported. -- 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-200992-16-I5zIkA3sbW>