Date: Wed, 04 May 2016 17:16:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 209233] [patch] pthread_suspend_all_np races with check_suspend Message-ID: <bug-209233-16-Ss32D2scSs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209233-16@https.bugs.freebsd.org/bugzilla/> References: <bug-209233-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=3D209233 --- Comment #6 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Lawrence Esswood from comment #5) Yes, it is a bug that I left the old test in the loop condition. I left on= ly the check for THR_FLAGS_NEED_SUSPEND there, since it is cleared only on res= ume. WRT SIGCANCEL generated after loop exit and before thr_signal_unblock. The blocked signal list includes SIGCANCEL, thus the SIGCANCEL signal should be only delivered after unblock. Then typically we would re-enter _thr_ast() w= ith the different set of flags. --=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-209233-16-Ss32D2scSs>