pthread_rwlock_timedwrlock - lock a read-write lock for writing
int pthread_rwlock_timedwrlock(pthread_rwlock_t *restrict rwlock,
const struct timespec *restrict abstime);
The pthread_rwlock_timedwrlock() function shall apply a write lock to the read-write lock referenced by rwlock as in the pthread_rwlock_wrlock() function. However, if the lock cannot be acquired without waiting for other threads to unlock the lock, this wait shall be terminated when the specified timeout expires. The timeout shall expire when the absolute time specified by abstime passes, as measured by the clock on which timeouts are based (that is, when the value of that clock equals or exceeds abstime), or if the absolute time specified by abstime has already been passed at the time of the call.
The timeout shall be based on the CLOCK_REALTIME clock. The resolution of the timeout shall be the resolution of the CLOCK_REALTIME clock. The timespec data type is defined in the <time.h> header. Under no circumstances shall the function fail with a timeout if the lock can be acquired immediately. The validity of the abstime parameter need not be checked if the lock can be immediately acquired.
If a signal that causes a signal handler to be executed is delivered to a thread blocked on a read-write lock via a call to pthread_rwlock_timedwrlock(), upon return from the signal handler the thread shall resume waiting for the lock as if it was not interrupted.
The calling thread may deadlock if at the time the call is made it holds the read-write lock. The results are undefined if this function is called with an uninitialized read-write lock.
The pthread_rwlock_timedwrlock() function shall return zero if the lock for writing on the read-write lock object referenced by rwlock is acquired. Otherwise, an error number shall be returned to indicate the error.
The pthread_rwlock_timedwrlock() function shall fail if:
- The lock could not be acquired before the specified timeout expired.
The pthread_rwlock_timedwrlock() function may fail if:
- A deadlock condition was detected or the calling thread already holds the rwlock.
- The abstime nanosecond value is less than zero or greater than or equal to 1000 million.
This function shall not return an error code of [EINTR].
Applications using this function may be subject to priority inversion, as discussed in XBD Priority Inversion.
If an implementation detects that the value specified by the rwlock argument to pthread_rwlock_timedwrlock() does not refer to an initialized read-write lock object, it is recommended that the function should fail and report an [EINVAL] error.
pthread_rwlock_destroy, pthread_rwlock_rdlock, pthread_rwlock_timedrdlock, pthread_rwlock_trywrlock, pthread_rwlock_unlock
XBD Priority Inversion, Memory Synchronization, <pthread.h>, <time.h>
First released in Issue 6. Derived from IEEE Std 1003.1j-2000.
IEEE Std 1003.1-2001/Cor 2-2004, item XSH/TC2/D6/103 is applied, updating the ERRORS section so that the [EDEADLK] error includes detection of a deadlock condition.
The pthread_rwlock_timedwrlock() function is moved from the Timeouts option to the Base.
The [EINVAL] error for an uninitialized read-write lock object is removed; this condition results in undefined behavior.
return to top of page