Bug 429292 - fix pthread_cond_timedwait so that it uses absolute time FUTEX_WAIT command
fix pthread_cond_timedwait so that it uses absolute time FUTEX_WAIT command
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: distribution (Show other bugs)
1.0
All Linux
low Severity low
: ---
: ---
Assigned To: mrg-program-list
MRG Quality Engineering
:
Depends On: 429290
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-18 10:44 EST by Roland Westrelin
Modified: 2014-11-05 10:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Roland Westrelin 2008-01-18 10:44:05 EST
Description of problem:

This one is related to 429290.

pthread_cond_timedwait is implemented using the futex syscall with the
FUTEX_WAIT command. Because the FUTEX_WAIT command takes a relative time as a
timeout it cannot be used for realtime purposes and as a consequence,
pthread_cond_timedwait can't be either. 

We are asking that once 354744 is fixed, the pthread_cond_timedwait command be
fixed to take advantage of the new futex command.

The reason we are reporting the same issue in 2 different bugs is that, as a
first step, it would ok for us to only have the new futex command and not the
libc fix.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Note You need to log in before you can comment on or make changes to this bug.