Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 May 2016 15:19:06 +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-U4T1KELpEQ@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 #3 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Lawrence Esswood from comment #2)
Yes, my intent is to guarantee that the THR_FLAGS_SUSPENDED is never left
dandling, since we are not supposed to distinguish between previous and cur=
rent
suspension in suspend_common().

Then, why not simply clear THR_FLAGS_SUSPENDED in resume_common() ?  We
apparently do not care how much thread moved ahead returning from
check_suspend(), and the function unblocks SIGCANCEL only after it is ready=
 to
next suspend.

Could you provide a test case for the problem ?

--=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-U4T1KELpEQ>