Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 429292

Summary:	fix pthread_cond_timedwait so that it uses absolute time FUTEX_WAIT command
Product:	Red Hat Enterprise MRG	Reporter:	Roland Westrelin <roland.westrelin>
Component:	distribution	Assignee:	Nobody <nobody>
Status:	CLOSED UPSTREAM	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.0	CC:	jross
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:13:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	429290
Bug Blocks:

Description Roland Westrelin 2008-01-18 15:44:05 UTC

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:

Comment 2 Red Hat Bugzilla 2025-02-10 03:13:23 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.