Austin Group Bug Tracker
2014-06-05 14:47:54 UTC
A NOTE has been added to this issue.
======================================================================
http://austingroupbugs.net/view.php?id=622
======================================================================
Reported By: dalias
Assigned To: ajosey
======================================================================
Project: 1003.1(2008)/Issue 7
Issue ID: 622
Category: System Interfaces
Type: Omission
Severity: Objection
Priority: normal
Status: Under Review
Name: Rich Felker
Organization: musl libc
User Reference:
Section: XSH 2.9.5 Thread Cancellation
Page Number: unknown
Line Number: unknown
Interp Status: ---
Final Accepted Text:
======================================================================
Date Submitted: 2012-10-15 00:26 UTC
Last Modified: 2014-06-05 14:47 UTC
======================================================================
Summary: Disallow loophole for asynchronous cancellation of
any function
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000615 pthread_setcancelstate should be async-...
======================================================================
----------------------------------------------------------------------
(0002260) geoffclare (manager) - 2014-06-05 14:47
http://austingroupbugs.net/view.php?id=622#c2260
----------------------------------------------------------------------
The following part of the http://austingroupbugs.net/view.php?id=841 resolution
should be done in this bug
instead (so that it can be included in TC2):
At page 515 line 17840 section 2.9.5.4 Async-Cancel Safety add two
paragraphs:
<blockquote>If a thread has asynchronous cancellation enabled and is
cancelled during execution of a function that is not async-cancel-safe, the
behavior is undefined.
If a thread has deferred cancellation enabled, a signal catching function
is called in that thread during execution of a function that is not
async-cancel-safe, and the signal catching function calls any function that
is a cancellation point while a cancellation is pending for the thread,
without first disabling cancellation, the behavior is
undefined.</blockquote>
Issue History
Date Modified Username Field Change
======================================================================
2012-10-15 00:26 dalias New Issue
2012-10-15 00:26 dalias Status New => Under Review
2012-10-15 00:26 dalias Assigned To => ajosey
2012-10-15 00:26 dalias Name => Rich Felker
2012-10-15 00:26 dalias Organization => musl libc
2012-10-15 00:26 dalias Section => XSH 2.9.5 Thread
Cancellation
2012-10-15 00:26 dalias Page Number => unknown
2012-10-15 00:26 dalias Line Number => unknown
2013-04-25 16:19 Don Cragun Relationship added related to 0000615
2013-05-02 15:40 msbrown Interp Status => ---
2013-05-02 15:40 msbrown Summary Disallow loophope for
asynchronous cancellation of any function => Disallow loophole for asynchronous
cancellation of any function
2014-06-05 14:47 geoffclare Note Added: 0002260
======================================================================
======================================================================
http://austingroupbugs.net/view.php?id=622
======================================================================
Reported By: dalias
Assigned To: ajosey
======================================================================
Project: 1003.1(2008)/Issue 7
Issue ID: 622
Category: System Interfaces
Type: Omission
Severity: Objection
Priority: normal
Status: Under Review
Name: Rich Felker
Organization: musl libc
User Reference:
Section: XSH 2.9.5 Thread Cancellation
Page Number: unknown
Line Number: unknown
Interp Status: ---
Final Accepted Text:
======================================================================
Date Submitted: 2012-10-15 00:26 UTC
Last Modified: 2014-06-05 14:47 UTC
======================================================================
Summary: Disallow loophole for asynchronous cancellation of
any function
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000615 pthread_setcancelstate should be async-...
======================================================================
----------------------------------------------------------------------
(0002260) geoffclare (manager) - 2014-06-05 14:47
http://austingroupbugs.net/view.php?id=622#c2260
----------------------------------------------------------------------
The following part of the http://austingroupbugs.net/view.php?id=841 resolution
should be done in this bug
instead (so that it can be included in TC2):
At page 515 line 17840 section 2.9.5.4 Async-Cancel Safety add two
paragraphs:
<blockquote>If a thread has asynchronous cancellation enabled and is
cancelled during execution of a function that is not async-cancel-safe, the
behavior is undefined.
If a thread has deferred cancellation enabled, a signal catching function
is called in that thread during execution of a function that is not
async-cancel-safe, and the signal catching function calls any function that
is a cancellation point while a cancellation is pending for the thread,
without first disabling cancellation, the behavior is
undefined.</blockquote>
Issue History
Date Modified Username Field Change
======================================================================
2012-10-15 00:26 dalias New Issue
2012-10-15 00:26 dalias Status New => Under Review
2012-10-15 00:26 dalias Assigned To => ajosey
2012-10-15 00:26 dalias Name => Rich Felker
2012-10-15 00:26 dalias Organization => musl libc
2012-10-15 00:26 dalias Section => XSH 2.9.5 Thread
Cancellation
2012-10-15 00:26 dalias Page Number => unknown
2012-10-15 00:26 dalias Line Number => unknown
2013-04-25 16:19 Don Cragun Relationship added related to 0000615
2013-05-02 15:40 msbrown Interp Status => ---
2013-05-02 15:40 msbrown Summary Disallow loophope for
asynchronous cancellation of any function => Disallow loophole for asynchronous
cancellation of any function
2014-06-05 14:47 geoffclare Note Added: 0002260
======================================================================