Austin Group Defect Tracker

Aardvark Mark IV


Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Type Date Submitted Last Update
0000927 [1003.1(2013)/Issue7+TC1] System Interfaces Editorial Clarification Requested 2015-02-23 18:34 2015-05-07 16:16
Reporter dalias View Status public  
Assigned To
Priority normal Resolution Duplicate  
Status Closed  
Name Rich Felker
Organization musl libc
User Reference
Section pthread_cond_timedwait
Page Number unknown
Line Number unknown
Interp Status ---
Final Accepted Text
Summary 0000927: Conflicting requirements on pthread_cond_timedwait error reporting
Description Under RETURN VALUE, the specification for pthread_cond_[timed]wait reads:

"Except in the case of [ETIMEDOUT], all these error checks shall act as if they were performed immediately at the beginning of processing for the function and shall cause an error return, in effect, prior to modifying the state of the mutex specified by mutex or the condition variable specified by cond."

However, several of the specified errors deal with conditions which occur during re-locking of the mutex after the condition variable wait completes, and obviously can't be diagnosed before the mutex is unlocked. These include EOWNERDEAD and ENOTRECOVERABLE.
Desired Action Change the text:

"Except in the case of [ETIMEDOUT], all these error checks shall act as if they were performed immediately at the beginning of processing for the function and shall cause an error return, in effect, prior to modifying the state of the mutex specified by mutex or the condition variable specified by cond."

to:

"Error checks for [EINVAL] and [EPERM] shall act as if they were performed immediately at the beginning of processing for the function and shall cause an error return, in effect, prior to modifying the state of the mutex specified by mutex or the condition variable specified by cond."
Tags No tags attached.
Attached Files

- Relationships
duplicate of 0000749Closed pthread_cond_[timed]wait() immediate errors 

-  Notes
(0002560)
geoffclare (manager)
2015-02-24 09:24

This is already being fixed in TC2 via 0000749

- Issue History
Date Modified Username Field Change
2015-02-23 18:34 dalias New Issue
2015-02-23 18:34 dalias Name => Rich Felker
2015-02-23 18:34 dalias Organization => musl libc
2015-02-23 18:34 dalias Section => pthread_cond_timedwait
2015-02-23 18:34 dalias Page Number => unknown
2015-02-23 18:34 dalias Line Number => unknown
2015-02-24 09:24 geoffclare Note Added: 0002560
2015-02-24 09:24 geoffclare Relationship added duplicate of 0000749
2015-05-07 16:16 nick Interp Status => ---
2015-05-07 16:16 nick Status New => Closed
2015-05-07 16:16 nick Resolution Open => Duplicate


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker